Enabling or disabling a workflow returns the new state

POST /api/v2/workflows/:id/enable and POST /api/v2/workflows/:id/disable now return the workflow as it is after the change. Before, the response could show the old status and disabled values (an enable answered draft, a disable answered live) even though the change had been saved, so a script that checked the response thought the call had failed.

Both endpoints now also update the workflow's updated_at, and switching a workflow on or off through the API goes through the same save as the toggle in the app. A workflow that no longer passes validation (for example, one with an empty name) can still be disabled, but enabling it returns 422 with the validation errors.

Agent examples: switch a workflow live and trust the response instead of polling · sync workflows changed since the last run by updated_at

Resources: Enable Workflow · Disable Workflow
Building with an AI agent? Point it at the Workflows skill.