AI automation case study
Workflow Failure Alerting
A reusable n8n error workflow that sanitizes failure details, alerts the owner in Google Chat, and records whether the alert was delivered.
- Status
- Prototype
- Origin
- n8n
- Date
- 2026-08-30
Reusable n8n failure-alert workflow with sanitization, Google Chat notification, delivery confirmation, and fallback recording
Open full-size imageProject proof
Watch the proof film
A short local film made from privacy-reviewed project captures. No contact records or client identities are shown.
Local privacy-reviewed proof film
Challenge
What needed to change
A failed automation needs enough context for fast diagnosis, but raw payloads and stack traces can expose sensitive information, while a blind retry can duplicate an external action.
System
How the system works
An n8n Error Trigger captures the failed workflow, then a code step keeps only safe workflow, execution, node, severity, time, and deduplication metadata. Google Chat receives the limited summary, and the workflow records either a sent alert or an alert-delivery failure.
- Trigger
- A connected business workflow reports a failure
- Output
- Sanitized Google Chat alert plus SENT or FAILED state
- Control
- Check for duplicate external actions before retrying
Outcome
What is supported by the record
The current capture shows failure intake, sanitization, owner notification, delivery confirmation, and fallback branches in one reusable workflow. It provides operational visibility without claiming a production monitoring SLA or automatic recovery.
Screenshot
Current privacy-reviewed n8n canvas capture
Safety
Stack traces and raw payloads stay out of the alert
Fallback
Alert delivery success and failure are recorded separately
Tools
Connected tools and methods
- n8n
- Error Trigger
- Code nodes
- Google Chat
- Deduplication metadata
- Failure routing
Next step