Intercom incoming webhook setup guide | Incoming Webhooks

Prerequisites

Intercom account
EventStream/AudienceStream account

How it works

Intercom offers a Webhook API that sends outgoing requests to an endpoint that you specify. These requests act like push notifications to EventStream to inform it about things that happened in your Intercom account. When you add the Intercom data source in the Customer Data Hub (CDH), a unique endpoint is generated. This endpoint is used to configure the Intercom webhook. After it is configured, you can create subscriptions based on topics and receive related push notifications to automate use cases, stay informed, and increase productivity.

Intercom data source

The Intercom data source generates a unique URL to use as the HTTP POST URL in your Intercom configuration. The URL is generated in the following format:

https://collect.tealiumiq.com/integration/event/ACCOUNT/PROFILE/DATA_SOURCE_KEY

To add the Intercom data source to your Tealium CDH profile, see Data Sources. After adding and connecting the data source, save and publish your profile.

Intercom setup

After you generate your data source endpoint, use the following steps to go to your Intercom account and create the webhook.

Log in to your Intercom account.
Navigate to your applications.
Select the application you want to configure.
Go to Configure > Webhooks.
For your Intercom data source, specify the request endpoint URL generated by Tealium, as described in the previous section.
Select the topics that you want to receive notifications about.

Events and attributes

All incoming Intercom event attributes are automatically prefixed with intercom_. For example, Intercom will send the the data.item.conversation_message.type attribute to Tealium and it will be converted to intercom_data_item_conversation_message_type (all lowercase).

For a full list of webhook events and attributes generated by Intercom, go to Intercom - Webhook Models.

Event Attribute	Type	Example
`intercom_type`	String	“notification_event”
`intercom_id`	String	“notif_4e3504a3-ba3f-46dc-ab48-8e4d5bdfdf4e”
`intercom_created_at`	Number	“1571080403”
`intercom_topic`	String	“conversation.admin.closed”
`intercom_data_type`	String	“notification_event_data”
`intercom_data_item_type`	String	One of the following: “conversation” “user” “contact” “usertag” “ead” “contacttag” “visitor” “event” “ping”
`intercom_data_item_id`	String	“24098479713”
`intercom_data_item_user_type`	String	“user”
`intercom_data_item_user_email`	String	“wz1996@gmail.com”
`intercom_data_item_assignee_type`	String	“admin”
`intercom_data_item_assignee_email`	String	“weibin.zhong@intercom.io”
`intercom_data_item_conversation_message_subject`	String	“Hello”
`intercom_data_item_conversation_message_body`	String	“<p>This is a new conversation</p>”
`intercom_data_item_conversation_parts_conversation_parts`	List of objects	“[{“type”:“conversation_part”, “id”: “3928295317”},{“type”: “conversation_part”, “id”: “3928295318”}]”
`intercom_data_item_tags_tags`	List of objects	“{“type”: “tag”, “id”: “2913705”, “name”: “API”}, {“type”: “tag”, “id”: “2914621”, “name”: “Feature request”}]”
`intercom_data_item_id`	String	“530370b477ad7120001d”
`intercom_data_item_user_id`	String	“25”
`intercom_data_item_email`	String	“wash@serenity.io”
`intercom_data_item_phone`	String	“+1123456789”
`intercom_data_item_name`	String	“Hoban Washburne”
`intercom_data_item_company_id`	String	“6”
`intercom_data_item_event_name`	String	“invited-friend”

Prerequisites

How it works

Intercom data source

Intercom setup

Events and attributes

Vendor documentation