How to Disable Workflow Execution in n8n

The simplest way to disable a workflow is to toggle the Active switch. Open the workflow in the n8n editor and look at the top-right corner of the canvas. The Active toggle shows green when the workflow is active and grey when it is inactive. Click the toggle to switch it off. This immediately stops all triggers: webhook URLs return 404, cron schedules stop firing, and event-based triggers stop listening. Currently running executions are not interrupted — they finish before the deactivation fully takes effect. The workflow remains in your list and can be re-activated at any time.

Sometimes you want to stop part of a workflow without deactivating the whole thing. Right-click on any node and select Deactivate Node (or press D with the node selected). Deactivated nodes are greyed out and skipped during execution. The workflow continues to run but skips the deactivated nodes and everything downstream of them. This is useful for temporarily disabling a notification node, an expensive API call, or a database write while keeping the rest of the workflow running.

For bulk operations or automated maintenance, use the n8n REST API to deactivate workflows programmatically. First, enable API access in n8n settings and create an API key. Then use the PATCH endpoint to update a workflow's active status. You can script this to deactivate all workflows before a maintenance window and re-activate them afterward.

1# Deactivate a single workflow by ID
2curl -X PATCH https://n8n.example.com/api/v1/workflows/12345 \
3  -H 'X-N8N-API-KEY: your-api-key-here' \
4  -H 'Content-Type: application/json' \
5  -d '{"active": false}'
6
7# List all active workflows
8curl -s https://n8n.example.com/api/v1/workflows?active=true \
9  -H 'X-N8N-API-KEY: your-api-key-here' | jq '.data[] | {id, name}'
10
11# Deactivate ALL active workflows (maintenance script)
12for id in $(curl -s https://n8n.example.com/api/v1/workflows?active=true \
13  -H 'X-N8N-API-KEY: your-api-key-here' | jq -r '.data[].id'); do
14  curl -X PATCH "https://n8n.example.com/api/v1/workflows/$id" \
15    -H 'X-N8N-API-KEY: your-api-key-here' \
16    -H 'Content-Type: application/json' \
17    -d '{"active": false}'
18  echo "Deactivated workflow $id"
19done

During maintenance windows, team members might accidentally re-activate workflows. To prevent this, combine workflow deactivation with other safeguards. Add a note to the workflow description indicating it is under maintenance. If n8n supports user roles, temporarily restrict editor access. For critical systems, you can also block the n8n webhook port at the firewall level or stop the n8n process entirely during maintenance. After maintenance, verify each workflow works correctly before re-activating it.

After maintenance or debugging is complete, re-activate workflows by toggling the Active switch back on or using the API with active: true. After activation, verify each workflow by checking that triggers are responding (send a test webhook request), schedules are running (check the next execution time), and the execution history shows successful runs. For critical workflows, send a test event through the entire pipeline to confirm end-to-end functionality before considering the maintenance complete.

1# Re-activate a workflow via API
2curl -X PATCH https://n8n.example.com/api/v1/workflows/12345 \
3  -H 'X-N8N-API-KEY: your-api-key-here' \
4  -H 'Content-Type: application/json' \
5  -d '{"active": true}'
6
7# Verify webhook is responding
8curl -s -o /dev/null -w "%{http_code}" \
9  -X POST https://n8n.example.com/webhook/my-workflow \
10  -H 'Content-Type: application/json' \
11  -d '{"test": true}'