Skip to main content
Version: 4

App connector vs REST connector

App connector vs REST API connector​

REST connector is often used in scenarios where there is a need to connect to a third-party API. This could be for fetching data, sending data, or triggering actions on the third-party system.

  1. REST connectors are straightforward to use. They provide a simple way to connect to any REST API.
  2. Generally, it is used for simple REST API operations that do not involve complex request building.

If you need to integrate with an application that has a complex API, an app connector can be used to closely align with your application’s requirements and usage. App connectors provide the below capabilities out of the box that a REST connector doesn't have.

  1. Enables incremental data sync -- reading new/updated records.

  2. Handles the authentication process with the application, which can be complex and time-consuming to set up with a generic REST connector.

  3. Offers advanced features like pagination and batch operations that are not available with a generic REST connector.

  4. Allows to apply data filters to process records that you want (supports client-side filter on data fields that are not supported by API).

  5. Provides ID references and lookups for Update/Upsert operations.

  6. Supports dynamic schema and custom objects/fields.

However, developing an app connector could be time-consuming and complex in comparison to creating a REST connector. If the API interactions are relatively simple and don’t require complex authentication, or advanced features (like pagination, and batch processing), a generic REST connector might suffice.