Close Conversation: 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
Conversation ID conversation_id	string	Required	Intercom conversation ID — numeric string. Find via List Conversations.
Admin ID admin_id	string	Required	The admin closing the conversation
Closing Message body	string	Optional	Optional message when closing

Sample request

{
  "conversation_id": "e.g. 123456",
  "admin_id": "e.g. 12345",
  "body": "e.g. Hi there, thanks for reaching out."
}

Returns

{
  "id": "123456",
  "state": "closed"
}

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

FAQ

Questions about Close Conversation.

What does the Close Conversation action do in Intercom?

Closes an Intercom conversation. Use to auto-close stale conversations on inactivity or after a bot fully resolves the issue.

What inputs does Close Conversation require?

Required: Conversation ID, Admin 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 Close Conversation support batch operations?

Yes. Run Close Conversation 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