Everything for automating chatwoot-cli: output formats and headless/CI use. Need a command? See Commands. For shell completion setup, see Getting started.Documentation Index
Fetch the complete documentation index at: https://developers.chatwoot.com/llms.txt
Use this file to discover all available pages before exploring further.
Output formats
Every command takes-o / --output:
| Format | Flag | Use it for |
|---|---|---|
| Text table | (default) | reading at a glance |
| JSON | -o json | piping to jq, full API response |
| CSV | -o csv | spreadsheets, data exports |
| IDs only | -q / --quiet | shell pipelines |
Text (default)
Human-readable tables:JSON
Full API response, ready forjq:
CSV
Quiet — IDs only
-q prints just the IDs, one per line — perfect for xargs:
Headless / CI use
The OS keyring isn’t available in most CI environments. SetCHATWOOT_API_KEY to override the saved token:
--account to target a specific account:
-v / --verbose to print every HTTP request and response to stderr — handy when something looks wrong.
Tips
-qis your friend — every list command supports it, everyxargspipeline starts with it.- Pipe to
jqearly and aggressively;-o jsonreturns the full Chatwoot response, not a slimmed-down view. - Use
--no-colorwhen redirecting text output to a file or another program that doesn’t strip ANSI codes. chatwoot --helpandchatwoot <command> --helpare exhaustive — the CLI’s help is generated from the same definitions that drive the binary.

