Skip to main content

Prerequisites

  • Your Intercom access token
  • An Intercom admin or bot user ID

Setup

1

Get your Intercom access token

In Intercom, follow the authentication guide to create an access token.
2

Configure in Courier

Install the in Courier and enter your access token and user ID.

Profile requirements

Intercom addresses the recipient by user ID, nested under intercom.to.id on the profile. Courier assumes the user is of type user. Store it once with , which merges into the profile and creates it if it does not exist:
Then send to user_id and Courier resolves the address. For a one-off with no stored profile, pass it inline instead: "to": { "intercom": { "to": { "id": "INTERCOM_USER_ID" } } }.

Send by user id

The call in every language, and the rest of the profile object.

Send to a recipient

Courier reads intercom off the saved profile, so preferences apply and the value can change without touching this code.

Overrides

covers the two levels and which one wins. A provider override changes what Courier sends as an Intercom Message. Overrides are deep-merged into the request: fields you set replace their counterparts, and everything you leave out is still sent. You can override the message body and the From User ID. This example overrides both:
Other supported overrides are documented in the Intercom API reference.

Provider details

Courier recommends routing to the channel. Naming this key in routing.channels instead is supported, and sends through just this provider.

Send to a specific provider

When that is worth doing, and what you give up: failover, channel priority, and providers you add later.