ActionTidioUpdated May 2026

How do I list Tidio chat conversations?

Short answer: Drop the "Tidio → List Conversations" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Tidio actions

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
Limit limit	string	Optional	—

Sample request

{
  "limit": "{{trigger.limit}}"
}

Returns

{
  "data": [
    {
      "id": "cnv_abc",
      "status": "open",
      "visitor": {
        "email": "jane@x.com"
      }
    }
  ]
}

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.

Google Sheets → Tidio

2 Google Sheets triggers

HubSpot → Tidio

18 HubSpot triggers

FAQ

Questions about List Conversations.

What does the List Conversations action do in Tidio?

Lists chat conversations in Tidio with their visitor and status. Good for periodic exports to a BI tool or for triage dashboards.

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 Tidio 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 Tidio's rate limits automatically so you don't have to throttle manually.

More actions