Short answer: Drop the "Tidio → 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 |
|---|---|---|---|
Limit limit | string | Optional | — |
{"limit": "{{trigger.limit}}"}
{"data": [{"id": "cnv_abc","status": "open","visitor": {"email": "jane@x.com"}}]}
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.