Analyze failed workflows with Claude via OpenRouter and log to Sheets with Slack, Email, Discord alerts

by Open Paws ✓ · 94 views · created 2026-01-05 · DevOps, AI Summarization

What this workflow does

This AI workflow has 14 nodes and runs when another workflow fails (error workflow). Along the way it connects Gmail, OpenRouter Chat Model, Google Sheets and Slack and 1 more.

How it runs

Trigger: When another workflow fails (error workflow).

1. Normalize Error Payload (Edit Fields (Set)): sets 12 fields: workflow_name, workflow_id, execution_id…
2. Prepare AI Context (Code): runs custom JavaScript code
3. AI Error Analysis (Basic LLM Chain): sends a prompt to an LLM, with model: OpenRouter Chat Model
4. Extract AI Confidence (Code): runs custom JavaScript code
5. Generate Error Signature (Code): runs custom JavaScript code
6. Prepare Log Record (Edit Fields (Set)): sets 15 fields: timestamp, workflowName, workflowId…
7. Log to Google Sheets (Google Sheets): append
8. Check Alert Fatigue (Code): runs custom JavaScript code
9. Send Email (Gmail): uses Gmail
10. Send Slack Message (Slack): uses Slack

…plus 2 more steps. See the full node list below.

Services it uses

GmailOpenRouter Chat ModelGoogle SheetsSlackDiscord

Before you upgrade to n8n 3.0

Nodes used (10)

• Error Triggern8n-nodes-base.errorTrigger
• Coden8n-nodes-base.code
• Edit Fields (Set)n8n-nodes-base.set
• Basic LLM Chain@n8n/n8n-nodes-langchain.chainLlm
• Gmailn8n-nodes-base.gmail
• OpenRouter Chat Model@n8n/n8n-nodes-langchain.lmChatOpenRouter
• Google Sheetsn8n-nodes-base.googleSheets
• Slackn8n-nodes-base.slack
• Discordn8n-nodes-base.discord
• HTTP Requestn8n-nodes-base.httpRequest

From the author

Who is this for This workflow is designed for n8n users who manage multiple production workflows and want to: - Receive intelligent, actionable error alerts instead of raw stack traces - Understand root causes without manually debugging every failure -…

View the original on n8n.io → Check your own copy