Customer support

Connect Intercom

Your application calls one EchoRelay URL. When Intercom changes its API, you update the mapping, not your application.

How Intercom signs requests

An access token for your own workspace, sent as a bearer token in the Authorization header. OAuth is for public apps that read other people's workspaces.

Can you connect it today?

Yes, for your own workspace. Add a bearer-token credential with its access token.

A sample mapping

Your application sends the first request below. The mapping turns it into the body of POST /contacts, shown second.

Your request

{
    "email": "ana@example.com",
    "name": "Ana Silva"
}

What Intercom receives

{
    "role": "user",
    "email": "ana@example.com",
    "name": "Ana Silva"
}

The mapping

{
    "$schema": "https://schemas.echorelay.dev/transform/mapping/v1.json",
    "root": {
        "type": "object",
        "id": "root",
        "properties": {
            "role": {
                "type": "constant",
                "id": "role",
                "value": "user"
            },
            "email": {
                "type": "field",
                "id": "email",
                "path": "email"
            },
            "name": {
                "type": "field",
                "id": "name",
                "path": "name"
            }
        }
    }
}

The grammar, the answer mapping and the dry run are in the mapping docs.

What you bring

This is not a ready-made connector. You bring a sample request or Intercom’s OpenAPI document, you or your agent write the mapping, and we run the integration you define.

Intercom facts on this page were read 2026-10-29 from Intercom API authentication, Intercom API reference: create a contact. Another service? Check it here.

Connect everything. Deploy nothing.

No credit card required.