list_runs
List Trigger runs for an organization, with status, tags, time filters, and pagination.
list_runs
List Trigger runs for an organization (scoped by the organization ownership tag).
Use this for history such as failed runs this week. If you already have a run_ ID, call get_run.
See Installation for auth and response_format.
Arguments
| Argument | Type | Required | Description |
|---|---|---|---|
organizationId | string | Yes | Organization ID. |
status | string[] | No | Status filters, for example EXECUTING, COMPLETED, FAILED. |
tag | string[] | No | Extra non-organization tags. |
pageSize | number | No | Page size, 1-100. |
pageAfter | string | No | Cursor for the next page. |
pageBefore | string | No | Cursor for the previous page. |
createdAtFrom | string | No | Inclusive created-at lower bound (ISO 8601). |
createdAtTo | string | No | Inclusive created-at upper bound (ISO 8601). |
createdAtPeriod | string | No | Relative window: today, week, or month. |
isTest | boolean | No | When true, only test runs. |
response_format | json or markdown | No | Default json. |
Example
{
"organizationId": "org_123",
"status": ["FAILED"],
"createdAtPeriod": "week",
"pageSize": 20
}Returns
JSON with success and data (Trigger list payload: runs plus pagination).