list-cloudflows
dci list-cloudflows [flags]
Returns a cursor-paginated list of CloudFlows.
dci list-cloudflows presents a curated table by default:
- Columns:
name,id,published,trigger(fromtriggerType),run status(fromlastExecutionStatus),last run (UTC)(fromlastExecutedTime), andnext run (UTC)(fromnextRun). - In interactive tables,
last run (UTC)andnext run (UTC)render in your local timezone (titled(local)); machine formats, agent mode, and--utckeep UTC — see Timestamps and timezones. --output jsonand explicit-C/--fieldsselections return the raw fields documented below.
Flows are addressed by ID only — export-cloudflow-flow, refine-cloud-flow,
test-run-cloudflow-flow, and the run commands take the literal id shown here; there is no
name resolution for flows. The API does not filter or sort this listing server-side, so use
--search to narrow it.
Examples
# Your CloudFlows, with the IDs that export, refine, and test-run take.
dci list-cloudflows
# Find flows by keyword (client-side, case-insensitive, scans every page).
dci list-cloudflows --search cleanup
# Every page as JSON, for scripts.
dci list-cloudflows --all --output json
# Browse in the full-screen viewer.
dci list-cloudflows -M interactive
Flags
| Flag | Type | Default | Example | Description |
|---|---|---|---|---|
--max-results | integer | 50 | Maximum number of flows to return (1–500). Defaults to 50. | |
--page-token | string | Opaque cursor for the next page, taken from pageToken in the previous response. Omit to start from the beginning. |
Every command also accepts the CLI-wide flags for output shaping — see Output formats and Table output options.
Output
Paginated list of CloudFlows.
By default dci renders the result as a table. Use --output json to get the full structure described below — see Output formats.
| Field | Type | Description |
|---|---|---|
items | array of object | List of CloudFlows. |
items[].id | string | |
items[].name | string | |
items[].description | string | |
items[].instructions | string | |
items[].published | boolean | |
items[].triggerType | string | |
items[].createTime | string (date-time) | |
items[].updateTime | string (date-time) | |
items[].lastExecutedTime | string (date-time) | |
items[].lastExecutionStatus | string | One of: "pending", "running", "complete", "pending-approval", "failed", "sleeping", "stopped". |
items[].nextRun | string (date-time) | Next scheduled execution time. null when the CloudFlow has no active schedule. |
pageToken | string | Opaque cursor for the next page. null when there are no more CloudFlows. |
rowCount | integer | Always null. Row count is not computed for this endpoint. |
Raw JSON schema
{
"type": "object",
"required": [
"items"
],
"properties": {
"items": {
"type": "array",
"items": {
"type": "object",
"required": [
"id",
"name",
"published",
"createTime"
],
"properties": {
"id": {
"type": "string"
},
"name": {
"type": "string"
},
"description": {
"type": "string"
},
"instructions": {
"type": "string",
"nullable": true
},
"published": {
"type": "boolean"
},
"triggerType": {
"type": "string",
"nullable": true
},
"createTime": {
"type": "string",
"format": "date-time"
},
"updateTime": {
"type": "string",
"format": "date-time",
"nullable": true
},
"lastExecutedTime": {
"type": "string",
"format": "date-time",
"nullable": true
},
"lastExecutionStatus": {
"type": "string",
"nullable": true,
"enum": [
"pending",
"running",
"complete",
"pending-approval",
"failed",
"sleeping",
"stopped"
]
},
"nextRun": {
"type": "string",
"format": "date-time",
"nullable": true,
"description": "Next scheduled execution time. `null` when the CloudFlow has no active schedule."
}
}
},
"description": "List of CloudFlows."
},
"pageToken": {
"type": "string",
"nullable": true,
"description": "Opaque cursor for the next page. `null` when there are no more CloudFlows."
},
"rowCount": {
"type": "integer",
"nullable": true,
"description": "Always `null`. Row count is not computed for this endpoint."
}
}
}
Errors
On failure, dci prints a single error message — with a hint when one is available — and exits with a typed code your scripts can branch on. See Errors and exit codes for the full contract.
HTTP status to exit code mapping
| HTTP status | Exit code | Error code | Meaning |
|---|---|---|---|
| 400 | 30 | VALIDATION_ERROR | The arguments or request body were rejected. Review the command's flags and payload. |
| 401 | 10 | AUTHENTICATION_FAILED | Not signed in, or the API token is invalid. Run dci login or check DCI_API_KEY. |
| 403 | 11 | PERMISSION_DENIED | The DoiT user or the active customer context does not have access. |
| 500 | 40 | API_SERVER_ERROR | The API failed to process the request. Retryable; contact DoiT support if it persists. |
Related
- export-cloudflow-flow — Export a flow as a portable bundle
- build-cloud-flow — Build a new CloudFlow from scratch
- refine-cloud-flow — Refine a CloudFlow from natural language intent
- test-run-cloudflow-flow — Test-run a flow
- list-cloudflow-flow-runs — List a flow's runs
- trigger-cloudflow-webhook — Trigger a webhook flow
- API reference: GET /cloudflow/v1/flows
Aliases: listcloudflows