ActionUnipileUpdated September 2026

How do I send a message through any connected messaging account via Unipile?

Short answer: You can send message in Unipile by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Unipile Send Message action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Send Message in Unipile — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Account ID
account_id
stringRequiredThe connected account ID to send from
Chat ID
chat_id
stringRequiredThe chat/conversation ID to send the message to
Message Text
text
stringRequiredThe message text to send
Sample request
{
"account_id": "e.g. acc_abc123",
"chat_id": "e.g. chat_abc123",
"text": "{{trigger.text}}"
}
Returns
{
"object": "MessageSent",
"message_id": "msg_abc123"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Send Message.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Send Message.

What does the Send Message action do in Unipile?
Sends a message through any messaging account connected via Unipile, hiding the per-provider differences behind a unified API. Most commonly used for LinkedIn DM automation.
What inputs does Send Message require?
Required: Account ID, Chat ID, Message Text. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Unipile returns an error?
The run history shows the failed step with its input and the error message Unipile returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Send Message support batch operations?
Run Send Message inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Unipile's rate limits.
More actions

Other Unipile actions.

Send Message in Unipile — start free