list_automation_runs

Lists the runs of one automation, newest first. Filter by status. Each run says whether the event matched, the flow was started, a rule skipped it or it failed.

Tool name	`list_automation_runs`
Permission	`automations:read`
`readOnlyHint`	true
`destructiveHint`	false
`idempotentHint`	true
`openWorldHint`	false
REST call	`GET /v1/automations/{automation_id}/runs`

#What it does

Only reads data. It changes nothing and sends nothing.

#Input

The tool takes one flat object. Path, query and body fields of the REST call are merged into it.

Name	Type	Required	Description
`automation_id`	string	yes	Automation ID.
`limit`	integer	no	Items per page (1 to 100, default 20). 1 to 100; default `20`
`cursor`	string	no	next_cursor from the previous page. Opaque; only valid with the same filters. up to 300 characters
`status`	string	no	Only runs with this status. one of: `received`, `matched`, `executed`, `skipped`, `failed`

#Result

The result has the same content as the REST answer. Lists have at most 50 items per page (default 20); use cursor for the next page.

Errors come back as a tool result with isError: true. The error codes are the ones in Errors.