Short answer: Drop the "Unipile → 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 account_id | string | Required | The connected account ID to send from |
Chat ID chat_id | string | Required | The chat/conversation ID to send the message to |
Message Text text | string | Required | The message text to send |
{"account_id": "e.g. acc_abc123","chat_id": "e.g. chat_abc123","text": "{{trigger.text}}"}
{"object": "MessageSent","message_id": "msg_abc123"}
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.