Short answer: Drop the "Chatwoot → 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 accountId | number | Required | Account ID |
Status status | options | Optional | Status. Options: Open, Resolved, Pending, All |
{"accountId": "{{trigger.accountId}}","status": "{{trigger.status}}"}
{"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.
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.