Short answer: Drop the "Chatwoot → 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 |
|---|---|---|---|
Account ID accountId | number | Required | Account ID |
Conversation ID conversationId | number | Required | Conversation ID |
Message content | string | Required | Message |
Type message_type | options | Optional | Type. Options: Outgoing (agent), Incoming (contact) |
{"accountId": "{{trigger.accountId}}","conversationId": "{{trigger.conversationId}}","content": "{{trigger.content}}","message_type": "{{trigger.message_type}}"}
{"id": 123,"content": "Hello!","created_at": 1712835600,"message_type": "outgoing"}
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.