workflows_list
ManagementList Workflows
List visual workflows.
Terminology: In Scenario, when a user says "apps" (e.g. "list my apps"), they usually mean workflows in "ready" status — use status="ready". Same idea for "my ready apps" or "deployable workflows".
Args:
- status: optional status filter. Values "draft" and "ready" are server-filtered (the API supports them natively, faster). Any other value (e.g. "running", "archived") falls back to a client-side filter applied to the returned page only — _workflowListStatusFilter metadata flags this case.
- limit: results per page (default 20, max 200)
- page_token: pagination token from a previous response (nextPaginationToken)
- team_id, project_id: required for OAuth callers
Returns: { workflows } array plus nextPaginationToken when more pages exist. When a non-server status filter is applied, the response also carries _workflowListStatusFilter.
Examples:
- "List workflows" -> (no required args beyond context)
- "List my apps" / "ready workflows" -> status="ready"
read-onlyidempotentopen-world
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| status | string | — | Optional status filter: return workflows whose status matches this string. 'draft' and 'ready' are server-filtered (faster); any other value falls back to a client-side filter on the returned page using the workflow's status or workflowStatus field. Scenario users often say "apps" to mean ready workflows — use action="list" with status="ready". |
| limit | number | 20 | Results per page. |
| page_token | string | — | Pagination token (list). |
| team_id | string | — | Team ID. Required if user belongs to multiple teams. |
| project_id | string | — | Project ID to scope the operation to. |
| response_format | enum(json | markdown) | json | Output format: 'json' for structured data, 'markdown' for human-readable text. |
Example Request
JSON
{
"team_id": "team_abc123",
"project_id": "proj_xyz789"
}Example Response
JSON
{
"workflows": [
{
"id": "wf_hero_pipeline",
"name": "Hero Pipeline",
"status": "ready"
}
]
}Common Use Cases
- List all workflows in a project (every status, e.g. draft and ready)
- When the user says "apps" or only wants deployable workflows, filter by status="ready"