Short answer: Drop the "Intercom → Assign Conversation" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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. |
Performing Admin ID admin_id | string | Required | The admin performing the assignment |
Assignee Admin/Team ID assignee_id | string | Required | Admin or team to assign to |
Assignment Note body | string | Optional | Message body content. Plain text unless the API specifies HTML/markdown. |
{"conversation_id": "e.g. 123456","admin_id": "e.g. 12345","assignee_id": "e.g. 67890","body": "e.g. Hi there, thanks for reaching out."}
{"id": "123456","assignee": {"id": "67890","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.
Triggered by anything in the catalog. Free tier available. No credit card.