On This Page
Intercom enables you to offer near real-time engagement and support to your current and target customers through a messaging like platform. Using Hevo’s Intercom connector, you can replicate all your Intercom data to your desired Destination database or data warehouse.
For creating Pipelines using this Source, Hevo provides you a fully managed BigQuery data warehouse as a possible Destination. This option remains available till the time you set up your first BigQuery Destination irrespective of any other Destinations that you may have. With the managed warehouse, you are only charged the cost that Hevo incurs for your project in Google BigQuery. The invoice is generated at the end of each month and payment is recovered as per the payment instrument you have set up. You can now create your Pipeline and directly start analyzing your Source data. Read Hevo Managed Google BigQuery.
- An active Intercom account.
Configuring Intercom as a Source
Click PIPELINES in the Asset Palette.
Click + CREATE in the Pipelines List View.
In the Select Source Type page, select Intercom as the Source.
In the Configure your Intercom Account page, click + ADD INTERCOM ACCOUNT.
In the Intercom Welcome page, sign in to your Intercom account.
In the screen that appears, click the drop-down icon and select the workspace that you want Hevo to access. The list of workspace objects, for which Hevo captures the data, are displayed. You can click the expand icon for each object to see the permissions that Hevo has requested.
Click Authorize access to allow Hevo to access the objects.
In the Configure your Intercom Source page, specify a suitable Pipeline Name. The Intercom account you are logged in with is displayed.
Click TEST & CONTINUE.
Proceed to configuring the data ingestion and setting up the Destination.
The first run of the Pipeline replicates all existing data for the selected objects to the Destination.
Historical Data: The first run of the Pipeline replicates all data that exists for the selected objects to the Destination.
Incremental Data: Each subsequent run of the Pipeline subsequent to the initial one loads the changed records for the past hour. We recommend to use hourly sync, to avoid any loss of data.
Schema and Primary Keys
Hevo replicates data for the following objects from your Intercom account. The primary key of the Destination table is the same as that of the ingested Source object.
|Admin||Represents teammate accounts having access to a workspace.|
|Company||Represents organizations using the product.|
|Conversation||Represents how you communicate with users in Intercom. A conversation is created when a contact replies to an outbound message, or when one admin directly sends a message to a contact.|
|Conversation Part||Represents individual entities that make up a conversation.|
|Contact||Provides details of the contacts within Intercom and specifies whether they are a
|Segment||Represents a group of contacts defined by rules that you set. When a contact is updated, it is automatically added to the segment if it matches those rules.|
|Tag||Allows you to label your contacts and companies, and list them using that tag.|
|Team||Represents a group of admins in Intercom.|
The Intercom API retrieves only the latest 500
conversation partsbelonging to each
The Intercom API indexes timestamp fields for the Contact object, such as
updated_at, as dates. As a result, you can search for contacts based on these timestamps only by day, and not hour, minute or second. For example, if you search for contacts with the
updated_atvalue greater than (the UNIX timestamp for) December 10, 2021 2:30 PM, all contacts updated from 12.00 AM of December 10, 2021 are fetched. This can mean re-ingestion of some Events, which counts towards your Events quota consumption. Read Searching for timestamp fields.
It can take a few minutes for a newly created contact to become available for searching. Therefore, the “greater than or equal to <timestamp>” condition may not always be honored, and such contacts may not be retrieved in the API response. Read Search for contacts for more information.
To avoid this scenario, Hevo uses a buffer of one hour while searching for the contacts.
Refer to the following table for the list of key updates made to this page:
|Date||Release||Description of Change|
|Dec-09-2021||NA||- Renamed the Limitations section to Source Considerations.
- Added the Source considerations about supporting only day-based timestamp values for querying the Contacts object and using a time buffer for the search to ensure all eligible Events are ingested.
|May-19-2021||1.63||- Updated the section, Data Model to include descriptions of objects.
- Added the section, Limitations.