Workflows
List a workflow's triggers
List a workflow’s schedules and other triggers — kind, timing, version pin and next fire time.
GET
List a workflow's schedules and other triggers
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.
v2 compatibility notes
GET /api/v2/workflows/listTriggers?workflowId=<workflowId>
Returns one page of a workflow’s schedules and other triggers, newest first. Each trigger shows its kind, its timing, whether it follows the active version or pins one, the org unit its fires run at, and when it fires next.
To change a trigger, use createTrigger, updateTrigger and the other trigger writes; to list triggers across workflows, use listScheduleRoster.
Authentication
External App credential or platform API key. Requires permissionworkflows:read, held at two homes:
- the workflow’s home org unit, and
- each trigger’s
orgUnitId, the org unit its fires run at. Runs that a trigger starts are recorded there, so a caller that reads the trigger must be able to read there too.
Query parameters
Rows to read for this page, 1 to 50 (one read decides at most 50 org units, and each trigger names one). A larger value is
400 too_big. Zero, negative, fractional, non-numeric, empty or repeated values answer 400.Paging
A page readslimit triggers and then leaves out the ones the caller cannot read, so a page can be short or empty while meta.hasMore is true. Follow meta.nextCursor until hasMore is false. Every trigger the caller can read arrives on some page.
Responses
data is an array of trigger objects. Each has the fields described in getTrigger.
Errors
Example
Authorizations
Query Parameters
Response
Trigger list

