Transform your n8n automation setup into a production-ready environment with comprehensive error handling and audit logging across all your workflows. This centralized logging workflow captures unhandled errors, stores detailed audit trails, and provides essential observability for enterprise-grade n8n implementations. What this workflow does This reusable error handling and logging system creates a centralized hub for monitoring all your n8n workflows. It automatically captures unhandled workflow errors using the n8n Error Trigger and stores technical error details in an ErrorLog Data Table. The workflow enables other automation processes to write business and audit events into an AuditLog Data Table, creating a comprehensive activity trail. The system enriches all log entries with valuable observability metadata including workflow name, workflow ID, execution ID, error messages, failed node information, severity levels, and correlation IDs. Built-in security features automatically redact sensitive values like passwords, tokens, API keys, and authorization headers before logging. Scheduled cleanup logic purges old log records based on your configurable retention period, keeping your data tables optimized. Use cases Production n8n environments requiring centralized error monitoring and audit trails Multi-workflow setups where consistent logging standards are essential SaaS operations teams needing detailed observability across automation processes Compliance requirements demanding comprehensive audit logging with data retention policies Development teams troubleshooting complex workflow failures across multiple automations Technical details Built using core n8n nodes including Error Trigger for automatic error capture, Data Table nodes for structured logging storage, Schedule Trigger for automated cleanup operations, Execute Workflow Trigger for cross-workflow integration, Code nodes for data processing and redaction logic, and Sticky Note nodes for configuration management. Setup takes approximately 10-15 minutes and requires creating two n8n Data Tables (AuditLog and ErrorLog) with specified column structures. Once activated, simply designate this workflow as the Error Workflow in your other automations to enable comprehensive logging coverage.
