Skip to main content

Authorization

Follow this guide to create a new Intercom credential that will allow Nexla to authenticate to and exchange data with your Intercom account.
intercom_api_auth.png

Intercom

Prerequisites​

To connect Nexla to Intercom, you need an Intercom account and either an Access Token (for accessing your own workspace) or an OAuth app (for integrations that access multiple workspaces). Access Tokens are the simpler option for most data integration use cases and are available immediately after creating an app in the Intercom Developer Hub.

Obtain an Intercom Access Token​

Intercom uses Bearer token authentication for API access. Each app you create in the Intercom Developer Hub is issued a unique Access Token that grants access to the workspace where it is installed. Follow the steps below to create an app and obtain your Access Token.

  1. Navigate to the Intercom Developer Hub and sign in with your Intercom account credentials.

  2. From the Developer Hub dashboard, click Your Apps in the top navigation, then click the New app button.

  3. Enter a name for the app in the App name field (for example, "Nexla Integration"). Select the workspace where you want to install this app from the Workspace dropdown. Then click Create app.

  4. Once the app is created, go to the Configure tab within your app, then select Authentication from the left-hand menu.

  5. On the Authentication page, locate the Access Token section. Your Access Token is displayed here. Copy this token — you will enter it when configuring the Nexla credential.

Keep your Access Token secure

Your Intercom Access Token provides direct access to your workspace data and should be treated like a password. Do not share it with third parties or commit it to source control.

Intercom Access Tokens are associated with a specific workspace and do not expire unless manually revoked. For more information, refer to the Intercom Authentication documentation.

Intercom API Rate Limits​

Intercom enforces rate limits on API requests. The default limit is 10,000 API calls per minute per app and 25,000 calls per minute per workspace. Nexla handles standard API requests within these limits, but for high-volume data flows you may want to review the Intercom Rate Limiting documentation for details on how limits are enforced and how to request higher limits if needed.

Regional API Endpoints​

Intercom workspaces can be hosted in three regions: United States, European Union, and Australia. By default, API calls to api.intercom.io are automatically routed to the correct region. If your workspace requires a specific regional endpoint, you can use api.eu.intercom.io (EU) or api.au.intercom.io (Australia) in the API Endpoint URL field when configuring data sources or destinations.

Create an Intercom Credential​

  • To create a new Intercom credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

Credential Name & Description​

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. They should be used to provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

Access Token​

  1. Enter the Intercom Access Token you copied from the Intercom Developer Hub in the Access Token field. This token is used as a Bearer token in the Authorization header of all API requests Nexla makes to the Intercom API.

    The Access Token field corresponds to the token displayed on the Configure > Authentication page of your app in the Intercom Developer Hub. Ensure you copy the full token string without any leading or trailing spaces.

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.