Automated Error Reporting from Automation to Monday.com - n8n Workflow

Automation Managers: Who need centralized visibility into system stability and performance.
DevOps Teams: Seeking automatic alerting and ticketing when critical n8n workflow pipelines fail.
Technical Users of n8n: Who want to ensure that all failed n8n automation runs generate actionable tasks.
System Administrators: Who rely on n8n templates for robust error monitoring.

Silent failures are the enemy of reliable automation. When a crucial n8n workflow breaks, the operations team needs immediate notification and a clear record of the incident. This specialized n8n template solves this problem by using the built-in Error Trigger n8n trigger to catch any exceptions from other workflows across your n8n environment.

Upon failure, this n8n workflow immediately logs a new item on a specified Monday.com board, populated with essential diagnostics like the workflow name, the exact error message, the stack trace, and the time of failure. This integration transforms abstract errors into concrete, trackable tasks, dramatically improving incident response time and operational efficiency. Deploying this n8n workflow is key to maintaining a highly reliable automation infrastructure.

This automation is initiated by a specific internal n8n trigger designed for monitoring system health:

1. Error Detection: The process begins with the Error Trigger n8n node. This special n8n trigger listens for execution errors originating from any other workflow configured to report failures to it. It catches the full context of the failure.


2. Item Creation: The workflow immediately proceeds to the first Monday n8n node. This node creates a new item (a task) on the designated Monday.com board. The item's name is dynamically set using the ID of the failed n8n execution.


3. Timestamping: The Date & Time n8n node is executed to capture the precise moment the error occurred, providing accurate temporal data for logging.


4. Data Extraction (Code n8n node): A crucial Code n8n node is used to process and escape the stack trace data from the Error Trigger. This ensures that complex, multi-line stack trace information can be correctly stored in the Monday.com long text column.


5. Item Update: Finally, the UPDATE Monday n8n node retrieves the data from the previous steps (Workflow Name, Error Message, Stack Trace from the Code node, and the current Date). It uses the Item ID generated in Step 2 to update the newly created task, populating specific columns in Monday.com with the detailed error information captured by the n8n trigger.

To deploy this comprehensive n8n workflow, follow these steps:

1. Import the n8n Template: Copy the provided JSON data and paste it into your n8n instance using the 'New' -> 'Import from JSON' function.


2. Configure Monday.com Credentials: Edit the 'Monday' and 'UPDATE' n8n node and connect them using your existing Monday.com API credentials. If you don't have them, create a new credential entry in n8n.


3. Specify Board and Group: In both Monday n8n nodes, ensure you update the Board ID and Group ID to match your specific error tracking board.


4. Map Column IDs (Critical Step): In the 'UPDATE' n8n node, you must replace the placeholder column IDs (e.g., columnidforworkflowname) with the actual column IDs from your Monday.com board. This is essential for the n8n node to map the data correctly.


5. Link Workflows to the n8n Trigger: For other n8n automations to report errors here, you must navigate to their Workflow Settings -> Error Handling and select this specific workflow (named 'Send n8n automation errors to a Monday.com board') to be triggered upon failure.


6. Activate: Save and activate the n8n workflow.

Error Trigger (n8n trigger):
Function: This is the entry point, listening for execution failures from other linked n8n workflows. It provides rich context on the failed execution.
Key Configuration: Defaults to catching all reported errors.
Monday (Create Error Item):
Function: Creates the initial placeholder task item on the Monday.com board.
Key Configuration: Uses an expression to name the item based on the execution ID of the failed n8n workflow.
Date & Time (n8n node):
Function: Generates a current timestamp for accurate logging of the error incident.
Code (GET STACKTRACE n8n node):
Function: Executes custom JavaScript to extract, process, and escape the stack trace string from the error payload, preparing it for storage in a long-text column in Monday.com.
UPDATE (Monday n8n node):
Function: Updates the newly created item with all necessary diagnostic data using the changeMultipleColumnValues operation.
* Key Configuration: Requires manual configuration of Monday.com column IDs to map inputs like Workflow Name, Error Message, and Stack Trace.