Short answer: You can reply to conversation in Intercom by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Intercom Reply to Conversation action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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) |
{"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."}
{"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.
Any of these apps can fire this action as part of a workflow.