- Integrations
- /
- Unipile
- /
- Actions
- /
- List Conversations
ActionUnipileUpdated May 2026
How do I list conversations across messaging accounts via Unipile?
Short answer: Drop the "Unipile → List Conversations" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
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 | Optional | Filter by connected account ID |
Limit limit | string | Optional | Maximum number of conversations to return |
Cursor cursor | string | Optional | Pagination 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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does List Conversations support batch operations?
Yes. Run List Conversations inside a Loop node to process arrays. Tiny Command handles Unipile's rate limits automatically so you don't have to throttle manually.
More actions
Other Unipile actions.
Action
List Messages
Lists messages in a specific Unipile conversation across the connected account types. Combined with List Conversations, gives you a cross-platform message history view.
ActionSend Message
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.
Send list conversations from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.