ActionUnipileUpdated September 2026

How do I list conversations across messaging accounts via Unipile?

Short answer: You can list conversations in Unipile by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Unipile List Conversations 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.

List Conversations 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
stringOptionalFilter by connected account ID
Limit
limit
stringOptionalMaximum number of conversations to return
Cursor
cursor
stringOptionalPagination cursor from previous response
Sample request
{
"account_id": "e.g. acc_abc123",
"limit": "10",
"cursor": "{{trigger.cursor}}"
}
Returns
{
"items": [
{
"id": "chat_abc123",
"name": "John Doe",
"object": "Chat",
"provider": "LINKEDIN",
"account_id": "acc_abc123",
"last_message": {
"text": "Thanks for connecting!",
"timestamp": "2025-03-15T10:00:00Z"
},
"unread_count": 0,
"attendees_count": 2
}
],
"cursor": "next_cursor_token",
"object": "list"
}

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

Triggered by

Apps that pair well as the trigger for List Conversations.

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

FAQ

Questions about List Conversations.

What does the List Conversations action do in Unipile?
Lists conversations from accounts connected via Unipile (LinkedIn, WhatsApp, Telegram, Instagram, etc.) under a unified shape. The starting point for any cross-platform inbox or outreach automation.
What inputs does List Conversations require?
List Conversations has no required inputs. Sensible defaults are applied if you leave fields blank.
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 List Conversations support batch operations?
Run List Conversations 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.

List Conversations in Unipile — start free