Intercom webhook

The Intercom webhook collects support and engagement activity: conversations started, replies from either side, conversations closed and rated, and contact changes.

Support conversations are a churn signal that rarely reaches the customer profile. This puts them next to revenue and product usage.

Available events

Each event is normalised onto a named stream, so you build segments and journey triggers on the event name rather than on the payload shape.

Endpoint

The collector path for Intercom events is:

https://<your collector host>/webhooks/events/intercom

Every request must carry the source token issued when you create the connection. A payload that cannot be attributed to a known source is rejected rather than stored against a default.

Historical load

Connecting Intercom runs a one-time historical load before the webhook takes over. It covers: Contacts, conversations and companies.

The connector reports connected only once that load finishes, so a complete profile is never mistaken for a partial one. Records that arrive in the overlap between the load and the first webhook event are de-duplicated on the vendor's own event id.

Backfilled records do not trigger journeys, workflows or experiments.

Setup

Intercom webhooks are configured on a Developer Hub app. Create the source in Intempt first.

Configure Intercom

1. Create an Intercom source on the Integrations page and copy the endpoint and token.

2. In the Intercom Developer Hub, open your app and go to Webhooks.

3. Paste the Intempt endpoint as the notification URL.

4. Subscribe to the topics listed above and save.

5. Send a test notification from the Developer Hub to confirm delivery.