Skip to content
For LLMsView as Markdown·

Intercom ​

Manage conversations, contacts, and companies with the Intercom API.

DetailValue
CategorySupport
Base URLhttps://api.intercom.io
AuthenticationBearer Token
Endpoints6
Connector keyintercom

Using Intercom in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick Intercom from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints ​

EndpointSummary
GET /conversationsList conversations
GET /conversations/{id}Get a conversation
POST /conversations/{id}/replyReply to a conversation
POST /contactsCreate a contact
POST /contacts/searchSearch contacts
GET /companiesList companies

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /conversations ​

List conversations

DetailValue
Operation IDsupport.listConversations
MethodGET
Path/conversations

Parameters ​

NameLocationTypeRequired
per_pagequeryintegerNo

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Intercom connection from the Connection dropdown.
  3. In the Operation dropdown, select support.listConversations.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Intercom API reference.

GET /conversations/{id} ​

Get a conversation

DetailValue
Operation IDsupport.getConversation
MethodGET
Path/conversations/{id}

Parameters ​

NameLocationTypeRequired
idpathstringYes

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Intercom connection from the Connection dropdown.
  3. In the Operation dropdown, select support.getConversation.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Intercom API reference.

POST /conversations/{id}/reply ​

Reply to a conversation

DetailValue
Operation IDsupport.replyToConversation
MethodPOST
Path/conversations/{id}/reply

Parameters ​

NameLocationTypeRequired
idpathstringYes

Request Body ​

FieldType
message_typestring
typestring
bodystring

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Intercom connection from the Connection dropdown.
  3. In the Operation dropdown, select support.replyToConversation.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Intercom API reference.

POST /contacts ​

Create a contact

DetailValue
Operation IDsupport.createContact
MethodPOST
Path/contacts

Parameters ​

No parameters.

Request Body ​

FieldType
rolestring
emailstring
namestring

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Intercom connection from the Connection dropdown.
  3. In the Operation dropdown, select support.createContact.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Intercom API reference.

POST /contacts/search ​

Search contacts

DetailValue
Operation IDsupport.searchContacts
MethodPOST
Path/contacts/search

Parameters ​

No parameters.

Request Body ​

FieldType
queryobject

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Intercom connection from the Connection dropdown.
  3. In the Operation dropdown, select support.searchContacts.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Intercom API reference.

GET /companies ​

List companies

DetailValue
Operation IDsupport.listCompanies
MethodGET
Path/companies

Parameters ​

NameLocationTypeRequired
per_pagequeryintegerNo

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Intercom connection from the Connection dropdown.
  3. In the Operation dropdown, select support.listCompanies.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Intercom API reference.