Short answer: Drop the "Intercom → Get 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. |
Display As display_as | options | Optional | How to render the conversation content |
{"conversation_id": "e.g. 123456789","display_as": "{{trigger.display_as}}"}
{"id": "123456789","read": true,"type": "conversation","state": "open","title": "Help with billing","source": {"body": "Hi, I need help with my bill.","type": "conversation"},"contacts": {"contacts": [{"id": "5f7b1a2","type": "contact"}]},"created_at": 1700000000,"updated_at": 1700086400,"conversation_parts": {"total_count": 1,"conversation_parts": [{"body": "Sure, let me look into that for you.","type": "conversation_part","author": {"id": "12345","type": "admin"},"created_at": 1700003600}]}}
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.