Short answer: Drop the "Intercom → Send Message" 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 |
|---|---|---|---|
Message Type message_type | options | Required | Message Type. Options: In-App, Email |
Subject subject | string | Required | Message subject line. |
Body body | string | Required | Message body content. Plain text unless the API specifies HTML/markdown. |
From (Admin ID) from_admin_id | string | Required | Intercom Admin/Teammate ID |
To (Contact ID) to_contact_id | string | Required | Intercom Contact ID |
{"message_type": "{{trigger.message_type}}","subject": "e.g. Quick update","body": "e.g. Hi there, thanks for reaching out.","from_admin_id": "{{trigger.from_admin_id}}","to_contact_id": "{{trigger.to_contact_id}}"}
{"id": "123","body": "<p>Hi there!</p>","type": "admin_message","subject": "Hello!","message_type": "inapp"}
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.