Output formats

The CLI emits results in one of two formats: JSON (machine-readable) or table (human-readable). Default is JSON.

Forcing a format

celigo flows list --format json
celigo flows list --format table

Or persist the choice on a profile:

celigo config set default_format table

Or per session:

export CELIGO_FORMAT=table

Priority: --format CLI flag > CELIGO_FORMAT env var > profile default_format > default (json).

Table format

Each resource type defines its own column set — commonly _id, name, and one or two business-relevant fields. Those columns are also what a list command requests from the API by default, so --format table and the default JSON listing carry the same fields.

_id                        name                        disabled  lastModified
-------------------------  --------------------------  --------  --------------------
5f83a9b2c7d3e8f1a2b3c4d5   Shopify → NetSuite orders   false     2026-04-21T12:15Z
6a1b2c3d4e5f6a7b8c9d0e1f   NetSuite → Salesforce       false     2026-04-20T09:02Z

If a resource type doesn't define columns (mostly custom RPC-style responses), the CLI falls back to JSON.

JSON format

For a single resource, get returns an object. list returns an array.

get returns the complete resource body. list returns a projected row by default: _id, name, and the fields behind the table columns. Pass --fields all for complete documents, or a comma-separated list for specific fields. See Global flags for the full projection rules.

# Projected rows: identity plus the table columns
celigo flows list

# Complete flow documents
celigo flows list --fields all

# Slice a projected listing further
celigo flows list --jq '.[] | {_id, name, disabled}'

Indentation

JSON is indented by two spaces when stdout is a terminal, and printed compact when it is piped or redirected. The compact form avoids sending whitespace through a pipeline. Both forms parse identically:

celigo flows list                    # indented, readable
celigo flows list | jq '.[0].name'   # compact
celigo flows list > flows.json       # compact

--jq

--jq <expr> runs the response through jq without piping:

celigo flows get 5f83a9b2c7d3e8f1a2b3c4d5 --jq '.pageGenerators[]._exportId'

--jq forces JSON output; it's incompatible with --format table.

On a list command, --jq also requests complete documents, so the expression can address any field. That holds only while --fields is absent — an explicit --fields projects the rows first, and fields outside the projection then resolve to null.

Pagination and format

list commands auto-paginate via Link headers (up to 50 pages by default). The full result set is returned as one flat array.

For body-paginated endpoints (like flows errors), the CLI follows nextPageURL in the response body and concatenates pages.

To inspect pagination manually, use --verbose (see Global flags).

Color

ANSI color is enabled when stdout is a TTY. Disable with NO_COLOR=1 (standard) or by piping output.