Short answer: Drop the "Unipile → List Messages" 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 |
|---|---|---|---|
Chat ID chat_id | string | Required | The conversation/chat ID to fetch messages from |
Limit limit | string | Optional | Maximum number of messages to return |
Cursor cursor | string | Optional | Pagination cursor from previous response |
{"chat_id": "e.g. chat_abc123","limit": "10","cursor": "{{trigger.cursor}}"}
{"items": [{"id": "msg_abc123","text": "Hi, are you available for a call?","object": "Message","chat_id": "chat_abc123","is_sender": false,"sender_id": "user_001","timestamp": "2025-03-15T10:00:00Z"},{"id": "msg_abc124","text": "Sure, let me know the time.","object": "Message","chat_id": "chat_abc123","is_sender": true,"sender_id": "me","timestamp": "2025-03-15T10:05:00Z"}],"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.