Short answer: Drop the "Intercom → Create 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 |
|---|---|---|---|
From Type from_type | options | Required | Who is initiating the conversation |
Contact ID from_id | string | Required | The Intercom ID of the contact starting the conversation |
Message Body body | string | Required | Initial message content (supports HTML) |
{"from_type": "{{trigger.from_type}}","from_id": "e.g. 5f7b1a2...","body": "e.g. Hi, I need help with..."}
{"id": "123456789","type": "conversation","source": {"body": "Hi, I need help with...","type": "conversation"},"contacts": {"contacts": [{"id": "5f7b1a2","type": "contact"}]},"created_at": 1700000000}
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.