Automatic Error Notification to LINE - n8n Workflow

• Users running mission-critical n8n workflow automation that require high reliability.


• Developers or administrators managing a self-hosted n8n instance who need instant monitoring.


• Anyone looking for robust error handling capabilities within their n8n environment.


• Users importing various n8n templates who need a centralized failure alert system.

Maintaining the reliability of your automated processes is critical. This specialized n8n workflow acts as a centralized monitoring tool, solving the common problem of undetected workflow failures. By setting this n8n template as the global error workflow, you ensure that every time any other n8n workflow fails, an immediate, detailed notification is sent to your LINE account.

This system uses the dedicated n8n trigger for errors to capture failure details—like the name of the failed workflow and the execution URL—and relays them via a standard HTTP Request n8n node to the LINE push API. This provides essential, real-time feedback, allowing you to quickly diagnose and fix issues, minimizing downtime for your entire n8n automation ecosystem. It is an indispensable safety net for any production-level n8n setup.

This powerful n8n workflow operates solely as a dedicated error handler for your entire n8n instance.

1. Error Detection (The n8n trigger): The process begins with the specialized Error Trigger n8n node. This n8n trigger is unique because it does not run on a schedule or webhook; instead, it activates only when another live n8n workflow encounters an unhandled error.


2. Data Extraction: Upon triggering, the Error Trigger n8n node automatically receives context about the failed execution, including the workflow name and a direct URL to the execution log.


3. Notification (HTTP Request n8n node): The flow immediately passes the error data to the HTTP Request n8n node. This node is configured to send a POST request to the LINE Messaging API (/v2/bot/message/push).


4. Message Formatting: The request body uses JSON to construct a clear, concise alert message, embedding the failed n8n workflow name and the execution URL using n8n expressions ({{ $json.workflow.name }} and {{ $json.execution.url }}). This ensures you get actionable information directly in your LINE chat.


5. Secure Transmission: The notification is sent using HTTP Header Authentication, relying on pre-configured LINE credentials to secure the communication. This completes the error handling cycle, providing instant alerts for any failed n8n workflow.

To deploy this essential n8n workflow template, follow these steps:

1. Import the n8n Workflow: Copy the provided JSON data and import it into your n8n instance via the 'New' menu > 'Import from JSON'.


2. Configure LINE Credentials: You need to set up a credential for the LINE Messaging API. This typically requires a Channel Access Token (used in the HTTP Header Authentication).

1. Update User ID: In the HTTP Request n8n node, open the 'JSON Body' field. Replace the placeholder with your specific LINE User ID or Group ID where you want to receive the error reports.


2. Activate and Set Error Workflow: Since this is a specialized error handler, you must globally designate it as your error workflow in your n8n instance settings (Settings > Error Workflow). Activate the n8n workflow switch once configured.

This n8n template utilizes specialized nodes for robust error capture and notification:

Error Trigger (n8n node):
Function: This is the primary n8n trigger that starts the workflow. It only activates when any workflow on the instance fails.
Key Configuration: Requires no internal configuration but must be set globally as the dedicated error handler workflow within n8n settings.

HTTP Request (n8n node):
Function: Sends the formatted error report to the LINE Messaging API via a POST request.
Key Configuration:
URL: https://api.line.me/v2/bot/message/push
Method: POST
JSON Body: Contains the alert structure, dynamically pulling the failed workflow.name and execution.url using n8n expressions. Crucially requires manual replacement of .
Authentication: Generic HTTP Header Authentication (requires a pre-configured LINE credential for the access token).