Connect Reverse ETL Source to Intercom v2 Beta
4 minute read
This guide takes you through the steps to connect a Reverse ETL source to the Intercom v2 destination.
The below steps assume that you have already set up a Reverse ETL source and configured the connection settings for the connected Intercom v2 destination.
You can connect multiple Reverse ETL sources to the LinkedIn Audience destination.
Setup
| Setting | Description |
|---|---|
| Choose object | Select the Intercom object from the dropdown. Note: RudderStack currently supports only the User object. |
| Sync mode | RudderStack supports only Mirror mode for this integration. |
Mapping settings
Use this section to map your warehouse columns to specific Intercom fields:
RudderStack does not support specifying multiple identifiers for the Intercom User object.
RudderStack supports the below Intercom Contact fields to which you can map your warehouse columns:
| Field | Data type | Description |
|---|---|---|
| Email Required, if User ID is not specified | String | User’s email address. |
| User ID Required, if Email is not specified | String or Null | Unique identifier for the contact. |
| Contact role | String | Contact’s role. |
| Last seen | Integer or Null | UNIX timestamp representing the time the contact was last seen. |
| Name | String or Null | Contact’s name. |
| Owner | Integer or Null | ID of the admin that has been assigned the ownership of the contact’s account. |
| Phone | String or Null | Contact’s phone number. |
| Signed up | Integer or Null | UNIX timestamp representing the time when the contact signed up. |
| Unsubscribed from Emails | Boolean | Determines whether the contact is unsubscribed from emails. |
| Avatar image URL | String or Null | Image URL containing the contact’s avatar. |
When you select User ID as the identifier and also provide Email in the mapping, RudderStack performs the lookup using Email, not User ID.
To use User ID for the lookup, include only User ID as the identifier without specifying Email in the mapping.
Schedule settings
RudderStack determines how and when to run a sync based on the sync schedule you set for your Reverse ETL connection.
| Schedule type | Description |
|---|---|
| Basic | Run syncs at a set interval, optionally starting from a specified time (UTC). If a start time is set, syncs run from that time until the end of that day. |
| CRON | Run syncs based on a specified CRON expression (in UTC). |
| Manual | Run syncs manually. |
Sync observability settings
| Setting | Description | ||||||
|---|---|---|---|---|---|---|---|
| Retain sync logs | This setting is toggled on by default and instructs RudderStack to store the sync logs in your warehouse. You can also configure the below settings:
| ||||||
| Retry failed records | This setting is toggled on by default and causes RudderStack to continually retry sending the failed records. | ||||||
| Retain and show failures | This setting is toggled off by default. Turn it on to have RudderStack write the error recorded for every failed record to a failed records table in your warehouse and show it in the sync’s failed records view. It applies from the next sync and can take up to a minute to reach your data plane.
|
Storing sync logs, snapshot tables, and failed records may incur additional warehouse costs.
record event structure
The Intercom v2 destination supports only record events.
A sample record event that RudderStack sends to Intercom is shown:
{
"action": "insert",
"channel": "sources",
"context": {
"sources": {
"job_id": "<job_id>",
"job_run_id": "<job_run_id>",
"task_run_id": "<task_run_id>",
"version": "v1.56.1"
}
},
"fields": {
"name": "RudderStack"
},
"identifiers": {
"external_id": "<external_id>"
},
"messageId": "a0ddf08f-9a3f-45ff-80b8-d5007aac29c2",
"receivedAt": "2024-11-19T11:12:39.917Z",
"recordId": "1",
"request_ip": "1.2.3.4",
"rudderId": "853ae90f-0351-424b-973e-a615e6487517",
"type": "record"
}FAQ
Why can’t I add a Reverse ETL source from the destination page?
The Reverse ETL feature supports only source-driven pipeline configuration. It means that you must configure a Reverse ETL source in RudderStack and then connect it to a new or existing destination. Note that this destination should not be connected to any other source.
See Reverse ETL FAQ for more information.
