Reply to 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.
Reply Type message_type	options	Required	Reply Type. Options: Comment (visible to customer), Note (internal, not visible to customer)
Replying As type	options	Required	Replying As. Options: Admin/Teammate, User
Admin ID admin_id	string	Optional	Required when replying as an admin. Your Intercom admin/teammate ID.
Message Body body	string	Required	Reply content (supports HTML)

Sample request

{
  "conversation_id": "e.g. 123456789",
  "message_type": "{{trigger.message_type}}",
  "type": "{{trigger.type}}",
  "admin_id": "e.g. 12345",
  "body": "e.g. Hi there, thanks for reaching out."
}

Returns

{
  "id": "123456789",
  "type": "conversation",
  "conversation_parts": {
    "conversation_parts": [
      {
        "body": "Thanks for reaching out! Let me help.",
        "type": "conversation_part",
        "author": {
          "id": "12345",
          "type": "admin"
        }
      }
    ]
  }
}

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

FAQ

Questions about Reply to Conversation.

What does the Reply to Conversation action do in Intercom?

Adds a reply (comment or note) to an existing Intercom conversation, as a specific admin or contact. The default action for AI-bot or autoresponder workflows.

What inputs does Reply to Conversation require?

Required: Conversation ID, Reply Type, Replying As, Message Body. 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 Reply to Conversation support batch operations?

Yes. Run Reply to 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