Intercom

Intercom connections give you access to your company’s customer engagement and marketing data from Intercom.

Source Setup

Etleap uses OAuth to authenticate with Intercom. The connection setup page in Etleap will forward you to your Intercom account to authorize API access. Note: If you see an error page containing “We’re having technical difficulties” after Etleap redirects you to Intercom during the oAuth setup, please go to Intercom’s sign in page and make sure that you are logged in.

Note

Prefer using an API? Go here and select Intercom under the Body header to start creating a connection via API.

What Data is Available?

Warning

Update-Mode Deletes Support

Deletes are not supported for update-mode entities with this connector.

You can create Intercom pipelines with the following entities:

Entity	Pipeline Mode	Iceberg Support
Admin	Replace	Batch
Admin Conversation Counts	Replace	Batch
Company	Update	-
Company Segments Counts	Replace	Batch
Company Tags Counts	Replace	Batch
Contact	Append	-
Conversation	Update	-
Conversation Counts	Replace	Batch
Conversation Parts	Update	-
Conversation Tags	Update	-
Counts	Replace	Batch
Event	Replace	Batch
Lead	Update	-
Note	Replace	Batch
Segment	Update	-
Subscription	Update	-
Tag	Replace	Batch
User Segments Counts	Replace	Batch
User Tags Counts	Replace	Batch

Key Considerations

Scrolling API

Etleap uses Intercom’s pagination API to enumerate records to fetch. There is a restriction on the number of records that can be listed via this API for certain entities. When there are more than 10,000 records for the following entities, Etleap uses the scrolling API to fetch data instead:

Company
Lead

The scrolling API only permits a single scroll context to be active at once. Etleap accounts for this and is able to handle multiple, concurrent pipelines that use the scrolling API. However, you may experience a reduction in performance if you have many Intercom pipelines.

Contact Entity

Intercom introduced a Contact entity in version 2.0 of their API. Contact replaces the User and Lead entities in the API and includes the same information as these entities. The Contact entity uses a different cursor-based mechanism to iterate the records that does not interfere with the scroll context used by the Company, Lead, and User entities. Be aware that Contact pipelines operate in Append mode while the other entities operate in Update mode. The User entity was deprecated on 12/12/2023 and new pipelines should use Contact instead.