Short answer: Drop the "Unipile → List Conversations" 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 | 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 |
{"account_id": "e.g. acc_abc123","limit": "10","cursor": "{{trigger.cursor}}"}
{"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.
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.