Error Trigger
The Error Trigger is a specialized, extremely powerful system node that serves as the ultimate safety net for your entire workspace. When any other active workflow in the workspace suffers an unhandled failure (e.g., node crash, unreachable API, unauthorized access), the nLink Engine instantly delegates power to this node, feeding it the exact error details. It allows you to build a single centralized 'Error Handling Workflow' (such as sending a Slack or Telegram alert) to monitor hundreds of workflows simultaneously.
What can you do with Error Trigger?
Global Workspace Safety Net
Acts as an invincible global listener. You only need to create ONE Error Trigger workflow to automatically protect and monitor every other workflow running inside your Workspace.
Rich Diagnostic Payload
When triggered, it automatically injects a wealthy JSON payload containing the exact identity of the failed Workflow, the Execution ID, timestamps, and the specific root-cause Error Message, allowing you to instantly pinpoint the problem.
Anti-Infinite-Loop Architecture
Built with enterprise-grade defensive mechanics. If the Error Handling workflow itself experiences a crash, the nLink Engine will deliberately suppress further triggers to absolutely prevent catastrophic infinite notification loops.
Detailed Usage & Configuration
Unlike standard triggers (e.g., Webhook or Manual Trigger) which are invoked by intentional user action or outside data, the Error Trigger is natively hooked into the deeply-embedded core lifecycle of the nLink Engine.
1. How it works
Simply drag the Error Trigger onto a blank canvas and connect it to your preferred notification node (such as HTTP Request to Telegram, or Gmail). Once you Publish this workflow, you're entirely finished. The Engine will automatically recognize this listener.
2. Consuming the Error Payload
Once a failure happens elsewhere, the Error Trigger will awaken and push out a structured JSON payload that looks exactly like this:
{
"workflow": {
"id": 12,
"code": "wf_123xyz",
"name": "Sync Shopify Orders"
},
"execution": {
"code": "exec_84x2m9",
"status": "error",
"url": "https://localhost/w/1/executions/exec_84x2m9"
},
"error": {
"message": "Node 'HTTP Request' failed: 401 Unauthorized"
}
}You can easily map these dynamic fields into your Slack message text using expressions like {{ $json.workflow.name }} and {{ $json.error.message }}.