Workflows
Reset a workflow draft to a version
Replace a workflow’s draft with a published version, discarding its unpublished edits.
POST
Reset a workflow draft to a version
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
POST /api/v2/workflows/resetDraft replaces the draft’s graph and settings with a published version’s (versionId; default: the active version), and returns {workflowId, draftBaseVersionId, nodeCount, edgeCount}.
Authentication
External App credential or platform API key, or a Personal key. Requires permissionworkflows:manage (an elevated permission) held at the platform scope, as the Console decides it; a key or app granted only at some org units receives 403, recorded, and nothing is written. Forge agents can never hold workflows:manage. Because the success answers a read, the credential’s scopes must include workflows:read as well (otherwise 403 naming it), and the workflow must be readable at its home (otherwise 404). A Personal key acts as its owner, narrowed by its scopes; an External App or platform key acts as itself. The change is stored and audited with that actor (for an app or platform key, with who granted it), under the Console’s own audit events.
Behavior
SendexpectedBaseVersionId (the draft’s base version you expect; null for none) to refuse with 409 if the draft moved to another base. Without it, concurrent draft edits are overwritten. A never-published workflow answers 409, and so does a graph over 200 nodes or 400 edges, which the API does not reset (use the Console).
Idempotency
Send anIdempotency-Key to make a retry safe: a same-key retry of a completed call within 24 hours returns the recorded result only while the caller still holds workflows:read and workflows:manage at the platform scope and the workflow still exists; otherwise 409 idempotency_result_unavailable, and the write never runs twice (see Idempotency). If an outcome is unknown, repeat with the same key or read the workflow; never retry under a new key.Authorizations
Headers
Body
application/json

