Intercom brings messaging products for sales, marketing & customer service to one platform, helping businesses avoid the stiff, spammy status quo and have real conversations that build real connections. Designed to feel like the messaging apps you use every day, Intercom lets you talk to consumers almost anywhere: inside your app, on your website, across social media and via email.
|Data blocking||check||Column level|
|History||check||Only tables with a
|API configurable||check||API configuration|
|Fivetran data models||check||Get the models: source / transform|
Follow our step-by-step Intercom setup guide to connect Intercom with your destination using Fivetran connectors.
This schema applies to all Intercom connections.
We capture the deletes for following objects, by leveraging Intercom webhooks and API:
Intercom doesn’t consider outbound messages without replies as conversations.
We found that if an end-user doesn’t reply to outbound messages (such as emails, posts, or chats), we can’t fetch the conversation IDs because the REST API does not return them. As a result, we can’t sync these conversations to your destination.
You may observe missing conversation IDs in your destination tables because they are not part of Intercom’s API response. We have submitted a feature request to Intercom to include the conversation IDs of all outbound messages in the API response.
The Intercom API does not provide us incremental updates for the
COMPANY_TAG_HISTORY tables. We re-import these tables once a week.