ActionChatwootUpdated September 2026

How do I list Chatwoot conversations?

Short answer: You can list conversations in Chatwoot by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Chatwoot List Conversations action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Conversations in Chatwoot — start free All 3 Chatwoot actions

List Conversations in Chatwoot — start free

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 accountId	number	Required	Account ID
Status status	options	Optional	Status. Options: Open, Resolved, Pending, All

Sample request

{
  "accountId": "{{trigger.accountId}}",
  "status": "{{trigger.status}}"
}

Returns

{
  "data": {
    "meta": {
      "all_count": 50
    },
    "payload": [
      {
        "id": 1,
        "status": "open",
        "contact": {
          "name": "John Doe",
          "email": "john@example.com"
        },
        "messages_count": 5
      }
    ]
  }
}

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 → Chatwoot

2 Google Sheets triggers

HubSpot → Chatwoot

18 HubSpot triggers

FAQ

Questions about List Conversations.

What does the List Conversations action do in Chatwoot?

Paginated conversations with filters by inbox, status, assignee. Useful for "what's in the queue this morning" capacity-planning workflows and for bulk-action workflows that operate on conversation sets.

What inputs does List Conversations require?

Required: Account ID. Every input accepts a static value or a variable from any upstream node in your workflow.

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 Chatwoot returns an error?

The run history shows the failed step with its input and the error message Chatwoot returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List Conversations support batch operations?

Run List Conversations inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Chatwoot's rate limits.

More actions

Other Chatwoot actions.

Action

Get Agent Profile

Returns an agent or contact profile by ID. Useful for resolving user IDs to readable identity in downstream notifications.

Action

Send Message

Posts a customer-facing reply (outgoing) or an internal team note (private). Routes via the conversation's originating channel by default. Useful for "AI-drafted response posted as private note for agent review" or for full-auto reply workflows on low-complexity tickets.

List Conversations in Chatwoot — start free