Deploy a new version of a workflow. The deployed version becomes available for running workflow runs.
When steps is omitted, the current draft is deployed as-is. When steps is provided, the given steps are deployed directly without modifying the draft.
Bearer authentication of the form Bearer <token>, where token is your auth token.
The type of object. Always "workflow_version".
The version number as a string, or "draft" for the draft version.
The time (in UTC) at which the object was created. Will follow the RFC 3339 format.
Example: "2024-03-21T16:45:00Z"
API version to use for the request. If you’re using an SDK, you can ignore this parameter. If you are not using an SDK and do not specify a version, you will either receive a 400 Bad Request or be set to a previous legacy version. See API Versioning for more details.
Optional step definitions. When provided, these steps are deployed directly without modifying the draft. When omitted, the current draft is deployed.
All configurable steps (EXTRACT, CLASSIFY, SPLIT, CONDITIONAL_EXTRACT, RULE_VALIDATION, EXTERNAL_DATA_VALIDATION) must include config when deploying. Unconfigured steps are rejected with a 400.
See the Configuring Workflows via API guide for step definitions, branching patterns, and examples.
