Error Handler

The shared error-notification handler for every National Commerce scenario. When any workflow fails, this one enriches the error with execution and workflow context and forwards it to an external alerting pipeline.

At a glance

• Status: Active.
• Trigger: Error Trigger, automatically invoked by other workflows when they fail. It has no production trigger of its own.
• Runs on: One failed execution per invocation.
• Talks to: n8n internal API (execution and workflow lookups) and Make.com (external alerting webhook).

How it works

1. The Error Trigger fires with the failed execution payload.
2. Get Execution Info fetches the full execution details by ID (retry on fail with a 3s wait).
3. Get Workflow Info looks up the failing workflow's name and URL (retry on fail with a 3s wait).
4. Send Error To Handler Scenario POSTs a JSON payload (client name, scenario name and URL, org URL, and the full errorDetails) to a Make.com webhook for downstream alerting.

Notes

• This is the shared error workflow set across the instance: nearly every active scenario names pqNfn3sZJQOn1GaG as its error workflow, so almost all failures funnel through here.
• All key nodes have retry-on-fail configured.
• Alerts route through Make.com, not native Slack.

Related

• Reattempt Failed Runs bulk-retries failed executions of a retired queue flow.
• Re-Do Error Runs repairs failed ShipHero-shipment ingestions.
• Scenario Backups: daily snapshot of every workflow.
• Purchase Order Update Handler: one of the many flows that reference this error workflow.
• See also Data flows.