List Conversations: 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
Per Page per_page	string	Optional	Per Page. e.g. "20"
Starting After starting_after	string	Optional	Cursor for pagination

Sample request

{
  "per_page": "20",
  "starting_after": "e.g. abc123"
}

Returns

{
  "type": "conversation.list",
  "pages": {
    "next": {
      "starting_after": "abc123"
    }
  },
  "conversations": [
    {
      "id": "123",
      "read": true,
      "state": "open",
      "title": "Help with billing"
    }
  ]
}

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

FAQ

Questions about List Conversations.

What does the List Conversations action do in Intercom?

Lists conversations in Intercom with filters for state, assignee, and update time. Used for queue dashboards, SLA reports, or warehouse exports.

What inputs does List Conversations require?

List Conversations has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List Conversations support batch operations?

Yes. Run List Conversations 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