Set Default Error Workflow in n8n via API (Batch Scan)
Set Default Error Workflow in n8n via API (Batch Scan)
Regular price
£55.99
Regular price
£55.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
âš¡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
Set Default Error Workflow in n8n via API (Batch Scan)
Regular price
£55.99
Regular price
£55.99
Sale price
Unit price
/
per
Set a Shared Default Error Workflow for Your n8n Automations—Automatically
This n8n workflow runs nightly (or on demand) and uses the n8n public REST API to scan all workflows in your instance, then sets the configured default error workflow for eligible workflows—without disrupting anything already configured.
What this workflow does
- Runs on a schedule: executes every night at 01:00, or you can manually trigger it.
- Fetches all workflows via API: calls the REST API and retrieves every workflow using cursor-based pagination.
-
Filters eligible targets:
- Skips workflows that are archived.
- Skips workflows tagged with the configured exclusion_tag.
- Skips the error workflow itself.
- Optionally skips workflows that already have an error workflow set using only_fill_empty.
-
Updates workflows safely: iterates through workflows in batches and updates each one via the API by setting
settings.errorWorkflowto your configured error_workflow_id, while keeping the existing workflow’s name, nodes, connections, and other settings intact. - Throttles requests: waits briefly between updates to avoid hammering the API.
Use cases
- After deploying a new SaaS, ensure every automation routes failures to your standard error handler.
- Reduce missed error handling when new workflows are created over time.
- Maintain consistency across teams by enforcing a shared default error workflow, while skipping excluded or archived workflows.
Technical details
-
API integration: n8n REST API with an API key provided as an HTTP header credential (e.g.,
X-N8N-API-KEY) used in both HTTP Request nodes. -
Configuration: set
n8n_base_urlanderror_workflow_id, then adjustonly_fill_emptyandexclusion_tag. - Nodes used: set, no op, wait, filter, split out, sticky note.
