workflow-builder

Source excerpt starting at line 1.

1# Workflow-Level Error Workflows2 3n8n has no global or instance-wide error workflow setting. Error workflows are4assigned per target workflow through workflow settings:5 6```ts7export default workflow('target-workflow-id', 'Target Workflow')8  .settings({ errorWorkflow: 'published-error-workflow-id' })9  .add(triggerNode);10```11 12`settings.errorWorkflow` must be the real workflow ID of a separate published13workflow whose published version contains an active Error Trigger node. Do not14use a workflow name, placeholder, `activeVersionId`, local SDK id, or invented15global identifier.16 17Use the no-global-setting rule as implementation guidance. Mention it to the18user only when they explicitly ask about, request, or reference global or19instance-wide error workflow behavior.20 21When creating an error workflow to attach to another workflow:22 231. Wait until the target workflow is published, then ask whether the user wants24   an error workflow for it.252. Build the error workflow as a separate workflow. It starts with an Error26   Trigger and sends the notification the user requested.273. Publish the error workflow with `workflows(action="publish")` before setting28   it on the target workflow: `settings.errorWorkflow` only accepts a published29   workflow, and publishing goes through HITL approval, so the user confirms it.30   This applies to the error workflow only; never publish the target workflow31   unless the user explicitly asks.324. Patch the original target workflow's source and set33   `.settings({ errorWorkflow: '<published-error-workflow-id>' })`, then call34   `build-workflow` for the original workflow. This assigns the error workflow35   only to that target workflow.36