List Workflow Triggers
List what starts a workflow. A workflow can have several triggers: a schedule, a webhook, an app event, or another workflow calling it.
Path
The workflow's id, from List Workflows.
Headers
Optional. The id of a child organization of your API key's company to act on. Leave it out to act on the key's own company. See Child organizations.
Query
draft (the default), published, or a version label from List Workflow Versions.
draft (the default, what the editor shows), published (what runs), or a version label from List Workflow Versions, such as 0.0.14.
Default: draft
RSQL expression used to filter list results.
Maximum number of rows to return.
Number of rows to skip.
Comma-separated sort fields; prefix with - for descending.
Comma-separated response fields to include.
Response fields
idstringThe trigger's id.
namestringThe trigger's display name.
appSlugstringWhat starts the workflow: schedule, webhook, runWorkflow (when another workflow calls it), or the app whose event does.
appVersionstringThe app version the trigger is pinned to. "0" for built-in triggers.
actionIdstringThe app event the trigger listens for. Null for a built-in trigger.
isDisabledbooleanTrue when the trigger is turned off.
isConfiguredbooleanWhether the trigger passed the editor's validation. Null when it was never validated.