Skip to main content

About

Full lifecycle control over workflow automations from your own code: list and inspect workflows, edit drafts, promote them live, pause and resume, trigger runs against records, control in-flight runs, read performance stats, and organize workflows into folders. All operations go through the developer API gateway — one endpoint, called by operationId. If you haven’t set up a key yet, start with the Developer API Overview.
Groups, versions, and draftsA workflow is a group of versions. At most one version is ACTIVE (live) and at most one is a DRAFT being edited. Reads return the group id used by every other workflow operation; version-level operations take a version id from getWorkflow.

Operations

Reading workflows (READ scope)

Building and shipping (WRITE scope)

Pausing and resuming (WRITE scope)

Run control (WRITE scope)

Folders (READ + WRITE scope)

Folders are a tree: each has an id, a name, a parentFolderId (null at the root) and a displayOrder. Every folder operation addresses folders by id.
Organization guardWorkflow operations are org-guarded on the ids you pass — a workflowId, folderId, or content-template id from another organization returns 403 forbidden. Listing and creating happen under your own org. See Authorization for the model.

Example

Trigger the live version of a workflow against one contact:
Full variable schemas, response shapes, and worked examples for every operation are available from the discovery endpoint.