Skip to main content
Intercom is a customer messaging platform that helps businesses communicate with their customers through live chat, email, and in-app messaging. It provides tools for customer support, lead generation, and user engagement, with features like automated messaging, customer data management, and integration with various business tools to enhance customer relationships and drive growth.

​
Configuring Intercom as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Intercom option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need to authorize Nekt to access your Intercom data. Click on the Intercom Authorization button and log in with your Intercom account. Grant the necessary permissions for the data you want to extract. The following configuration is available:
  • Start Date: The earliest date from which records will be synced (e.g., 2010-01-01). Used for the first full sync and when no previous state exists.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync - you can select all streams or pick specific ones that matter most to you. The available streams include companies, contacts, tickets, ticket types, conversations, and conversation parts.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
API Limitations

When syncing the Conversation Parts stream, be aware that Intercom’s API enforces a limit on the number of parts returned per conversation. If a conversation exceeds this limit, the connector will only extract up to the API limit, and any parts beyond that boundary will not be extracted. A warning is logged during extraction if a conversation is affected by this limitation.

​
Streams and Fields

Below you’ll find all available data streams from Intercom and their corresponding fields:
Stream for managing company information within your Intercom workspace.
Stream for managing contact information and their interactions with your business.
Stream for managing the different types of tickets configured in your Intercom workspace.
Stream for managing support tickets and their details.
Stream for managing conversations between your team and customers.
Stream providing the individual parts (messages, comments, state changes, etc.) that make up a conversation’s history.

​
Data Model

The following diagram illustrates the relationships between the core data streams in Intercom. The arrows indicate the join keys that link the different entities.

​
Implementation Notes

​
API Limitations & Search Behavior

  • Search Payload: Intercom’s /search endpoints require a query hash in the request body. When executing a full sync or an initial incremental extraction (where no start date or prior state exists), the connector automatically applies a match-all filter (> 0 timestamp) to ensure the API accepts the payload and fetches the complete historical data seamlessly.

​
Skills for agents

Download Intercom skills file

Intercom connector documentation as plain markdown, for use in AI agent contexts.