Get Contact: Intercom action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Contact ID contact_id	string	Required	Intercom contact ID — a 24-char hex string. Find via Search Contacts.

Sample request

{
  "contact_id": "e.g. 5e3a6d3c0a1b2c3d4e5f6789"
}

Returns

{
  "id": "abc",
  "role": "user",
  "type": "contact",
  "email": "user@example.com"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Contact.

What does the Get Contact action do in Intercom?

Retrieves an Intercom contact by ID with email, custom attributes, tags, and company memberships. The standard read after a trigger fires with an ID.

What inputs does Get Contact require?

Required: Contact ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Intercom returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Contact support batch operations?

Yes. Run Get Contact inside a Loop node to process arrays. Tiny Command handles Intercom's rate limits automatically so you don't have to throttle manually.

More actions