Intercom
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 by email.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | check | COMPANY_HISTORY, CONVERSATION_HISTORY, and CONTACT_HISTORY tables we leverage Intercom webhooks. We soft deletes using API for ADMIN, TAG, TEAM, SEGMENT, and SUBSCRIPTION_TYPE tables |
| History mode | check | _HISTORY suffix |
| Custom data | check | COMPANY_HISTORY, CONVERSATION_HISTORY and CONTACT_HISTORY tables |
| Data blocking | check | |
| Column hashing | check | |
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | ||
| Fivetran data models | check | |
| Private networking | ||
| Authorization via API | check |
Setup guide
Follow our step-by-step Intercom setup guide to connect Intercom with your destination using Fivetran connectors.
Schema information
This schema applies to all Intercom connections.
To zoom, open the ERD in a new window.Deleted data
We capture the deletes for following tables, by leveraging Intercom webhooks and API:
ADMINCOMPANY_HISTORYCONTACT_HISTORYCONVERSATION_HISTORYTAGTEAMSEGMENTSUBSCRIPTION_TYPE
Sync limitations
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. However, if you create messages through API and set the create_conversation_without_contact_reply value to true, we can fetch the conversations using Intercom's List Conversation API.
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_HISTORY and COMPANY_TAG_HISTORY tables. We re-import these tables once a week.