Intercom
Intercom ETL connector for data replication
Last updated
Intercom ETL connector for data replication
Last updated
Sign in to Daton
Select Intercom from Integrations page
Provide Integration Name, Replication Frequency, and History. Integration name would be used in creating tables for the integration and cannot be changed later
You will be redirected to Intercom login for authorizing Daton to extract data periodically. Login using Intercom credentials.
5. Post successful authentication, you will be asked to authorize the scopes required by Daton.
6. Post authorization, you will be redirected to Daton to select the tables and columns required.
7. Submit the integration
Integrations would be in Pending state initially and will be moved to Active state as soon as the first job loads data successfully on to the configured warehouse
Users would be able to edit/pause/re-activate/delete integration anytime
Users can view job status and process logs from the integration details page by clicking on the integration name from the active list
DataAttributes (Company, Contact, Conversation)
Purpose: You can fetch a list of all the company/contact/conversation data attributes. Data attributes are metadata used to describe your company, contact and conversation models.
Source API Documentation https://developers.intercom.com/intercom-api-reference/reference/data-attribute-model
Replication: Full Replication
Replication Key: NA
Fields
Leads, Users
Purpose: Fetch a list of all leads and users in two separate tables. Both the tables come from the 'Contacts' API which will specify whether they are a 'user' or a 'lead' through the 'role' attribute.
Source API Documentation https://developers.intercom.com/intercom-api-reference/reference/contacts-model
Replication: Key-Based Replication
Replication Key: updated_at
Fields
Companies
Purpose: You can fetch a list of companies. Companies allow you to represent commercial organizations using your product. Each company will have its own description and be associated with users.
Source API Documentation https://developers.intercom.com/intercom-api-reference/reference/company-model
Replication: Key-Based Replication
Replication Key: updated_at
Fields
Admins
Purpose: Admins are how you can view your teammates within Intercom that have access to a workspace.
Source API Documentation https://developers.intercom.com/intercom-api-reference/reference/admin-model
Replication: Full Replication
Replication Key: NA
Fields
Teams
Purpose: Teams are groups of admins within Intercom.
Source API Documentation https://developers.intercom.com/intercom-api-reference/reference/teams-model
Replication: Full Replication
Replication Key: NA
Fields
Tags
Purpose: A tag allows you to label your users and companies and list them using that tag. It also describes how users and companies can be tagged or untagged individually or in bulk.
Source API Documentation https://developers.intercom.com/intercom-api-reference/reference/tag-model
Replication: Full Replication
Replication Key: NA
Fields
Segments
Purpose: A segment is a group of your contacts defined by rules that you set. Contacts are automatically added to the segment every time the user updates to match those rules. Segments are different to tags, in that contacts need to be added to tags manually and tag members are not automatically managed.
Source API Documentation https://developers.intercom.com/intercom-api-reference/reference/segment-model
Replication: Full Replication
Replication Key: NA
Fields
Counts
Purpose: Counts are a legacy way to periodically obtain data for the purposes of tracking rates of change in contact and company data.
Source API Documentation https://developers.intercom.com/intercom-api-reference/reference#counts
Replication: Full Replication
Replication Key: NA
The total count object contains the summary of the following fields in a workspace. The count of tags and segments includes archived tags and segments.
Fields
Conversation Count
Purpose: The conversation count supplies global counts about your app's conversations
Source API Documentation https://developers.intercom.com/intercom-api-reference/reference#counts
Replication: Full Replication
Replication Key: NA
Fields
Admin Conversation Count
Purpose: The admin conversation count supplies per Admin counts
Source API Documentation https://developers.intercom.com/intercom-api-reference/reference/admin-conversations
Replication: Full Replication
Replication Key: NA
Fields
User Segment/Tag Count
Purpose: The count of tags and segments including archived tags and segments.
Source API Documentation https://developers.intercom.com/intercom-api-reference/reference/user-tag-counts
Replication: Full Replication
Replication Key: NA
Fields
Company User/Segment/Tag Count
Purpose: Company wise count of users, segments and tags including archived tags and segments.
Source API Documentation https://developers.intercom.com/intercom-api-reference/reference/user-tag-counts
Replication: Full Replication
Replication Key: NA
Fields
Conversations
Purpose: To fetch a list of all conversations. Conversations are how you can communicate with users in Intercom. They are created when a contact replies to an outbound message, or when one admin directly sends a message to a single contact.
Source API Documentation https://developers.intercom.com/intercom-api-reference/reference/conversation-model
Replication: Key-Based Replication
Replication Key: updated_at
Fields
Subscription Types
Purpose: List of all subscription types. A subscription type lets customers easily opt out of non-essential communications without missing what’s important to them.
Source API Documentation https://developers.intercom.com/intercom-api-reference/reference/conversation-model
Replication: Key-Based Replication
Replication Key: updated_at
Fields
| Key | Type | Description |
|---|---|---|
| Key | Type | Description |
|---|---|---|
| Key | Type | Description |
|---|---|---|
| Key | Type | Description |
|---|---|---|
| Key | Type | Description |
|---|---|---|
| Key | Type | Description |
|---|---|---|
| Key | Type | Description |
|---|---|---|
| Key | Type | Description |
|---|---|---|
| Key | Type | Description |
|---|---|---|