Actions44
- Execution Actions
- Monitoring Actions
- Scheduler Actions
- Tag Actions
- Workflow Actions
Workflow → Bulk Deactivate
AI-generatedSummary
Deactivates one or more n8n workflows through the n8n public API, one after another. It can optionally purge or stop in-flight executions, and it records a "drop before" timestamp so stale events can be filtered later.
Inputs
- Workflow Selection — How to pick targets: searchable list (one workflow), multiple from list, current workflow (needs the workflow to be saved), or by URL/ID. Default is list.
- Workflow Name or ID / Workflow Names or IDs / Workflow URL or IDs (required) — The workflows to deactivate, shown according to the selection mode. Manual mode accepts workflow URLs or comma-separated IDs. IDs are de-duplicated. Running with none selected throws an error.
- Force Stop Active Executions — If on, stops running and waiting executions of each workflow after deactivation. This only applies when Drop Events is off. Default is off.
- Drop Events Received While Inactive — Default is on. Records a pause timestamp in the node's workflow static data, then deactivates the workflow. After that it stops running executions and deletes new and waiting ones. This takes precedence over Force Stop.
- Continue On Error — Default is on. If a workflow fails, the error is recorded in the results and the remaining workflows are still processed. If off, the first failure throws and stops the run.
Output shape
One output item with a results array, one entry per workflow. Successful entries contain workflowId, workflowName, action ('deactivate'), success, message, graceful, forceStop, dropMissedEvents, pausedAt, dropBefore, purgedExecutions and stoppedExecutions. Failed entries contain workflowId, action, success:false and error.
purgedExecutions and stoppedExecutions list per-execution outcomes, and some of those can be individual failures even when the workflow itself deactivated. Deleting executions may not be supported by every n8n public API version. Requires the n8nApi credential. Requests retry up to 3 times on transient HTTP errors. The
gracefulfield comes from a parameter this operation does not expose, so it is always true. Per-item node errors only become error items if the node's Continue On Fail setting is on.
Examples
Example 1: Pause several workflows for a release and discard anything queued
Selection: Multiple From List; pick workflows; Drop Events: on; Continue On Error: on.
Example 2: Shut down workflows by ID but let in-flight runs be stopped explicitly
Selection: By URL or ID with 'id1,id2'; Drop Events: off; Force Stop: on.