Block 1 - 📘 README - Observability Core
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
How it works This workflow provides a reusable error handling, audit logging, and observability pattern for n8n workflows using two n8n custom Data Tables: and . It is designed to be used across mu...
n8n-nodes-base.stickynote, n8n-nodes-base.errortrigger, n8n-nodes-base.code, n8n-nodes-base.datatable, n8n-nodes-base.executeworkflowtrigger, n8n-nodes-base.scheduletrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Venkata V.
Original n8n.io sourceThis workflow provides a reusable error handling, audit logging, and observability pattern for n8n workflows using two n8n custom Data Tables: AuditLog and ErrorLog.
It is designed to be used across multiple workflows as a central logging workflow.
At a high level, it:
• Captures unhandled workflow errors using the n8n Error Trigger
• Stores technical error details in an ErrorLog Data Table
• Allows other workflows to write business/audit events into an AuditLog Data Table
• Adds useful observability metadata such as workflow name, workflow ID, execution ID, error message, failed node, severity, and correlation ID
• Redacts sensitive values such as passwords, tokens, API keys, and authorization headers before logging
• Includes scheduled cleanup logic to purge old log records after a configurable retention period
This template is useful for production-grade n8n setups where multiple workflows need a consistent and reusable logging approach.
Setup should take around 10–15 minutes.
Before using this template:
• Create two n8n Data Tables named AuditLog and ErrorLog
• Make sure the table columns match the expected structure described below
• Import this workflow into n8n
• Re-select your actual Data Tables in the Data Table nodes after import
• Set the retention period, for example 90 days, in the configuration node
• Activate the workflow
• In other workflows, select this workflow as the Error Workflow in Workflow Settings
• For audit logging, call this workflow using the Execute Workflow node
No hardcoded API keys are used in this template.
This template expects two n8n Data Tables.
| Column | Type |
|---|---|
| logID | String |
| logType | String |
| logDate | Date & Time |
| WorkflowName | String |
| WorkflowID | String |
| logData | String / JSON text |
| Column | Type |
|---|---|
| ErrorLogID | String |
| ErrorLogDate | Date & Time |
| ErrorMessage | String |
| WorkflowID | String |
| WorkflowName | String |
| BusinessData | String / JSON text |
Use Date & Time for logDate and ErrorLogDate.
The workflow writes ISO-8601 timestamps, for example:
2026-04-28T10:30:00.000Z
This allows the purge logic to delete records older than the configured retention period, for example 90 days.
Add Execute Workflow node and select this workflow. Send for audit logging:
{
"logType": "START | SUCCESS | WARNING | BUSINESS_ERROR",
"workflowName": "={{ $workflow.name }}",
"workflowId": "={{ $workflow.id }}",
"correlationId": "={{ $execution.id }}",
"businessKey": "invoice-123",
"message": "Invoice extracted successfully",
"payload": { "invoiceNo": "INV-123", "amount": 100 }
}
For automatic failures, configure each workflow setting: Error Workflow = this workflow.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Log errors and audit events with n8n Data Tables |
|---|---|
| Complexity | advanced |
| Nodes | 17 |
| Categories | Document Extraction |
| Author | Venkata V |
| Published | 28 Apr 2026 |
Use the JSON export at /data/workflows/15347/15347.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
How it works This workflow provides a reusable error handling, audit logging, and observability pattern for n8n workflows using two n8n custom Data Tables: and . It is designed to be used across mu...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Document Extraction use case.