Error handling: Send email via Gmail on execution or trigger-level errors
This error handling workflow emails detailed notifications on workflow execution and trigger errors.
It extends Send email via Gmail on workflow error template by covering trigger-level errors.
Features Get notifications on both main workflow trigger and execution time errors. Subject line will have failed workflow id, name, error source (execution or trigger), error message. Body will contain links to both failed and error handling workflows as well as execution or trigger-level error details. Body will also contain a machine readable and enriched JSON from Error Trigger describing the error.
Use this error handling workflow for as many workflows as you need.
Configiration Copy this workflow to your workspace and, optionally, move it under the project that contains your main workflow In this error handling workflow settings, set This workflow can be called by as appropriate In Config node, define your app url, notifications recipient email, and sender name (useful to build filters in your inbox) In Gmail node, create and select credentials In your main workflow settings, pick this error handling workflow in the Error Workflow field (How to...)
Related resources n8n Error Trigger documentation.
Author Reach out Olek on community.n8n.io Olek on n8n creators hub
Related Templates
Automatic News Summarization & Email Digest with GPT-4, NewsAPI and Gmail
📰 AI News Digest Agent: Auto News Summarizer & Email Newsletter Create an intelligent news curation system that automat...
Auto-classify Gmail emails with AI and apply labels for inbox organization
Who is this for? Professionals and individuals who receive high volumes of emails, those who want to automatically organ...
Generate Product Ad Copy & CTAs with GPT-4 for Slack and Airtable
⚡ AI Copywriter Pro: Instant Ad Copy & CTA Generator Transform product details into compelling marketing copy in second...
🔒 Please log in to import templates to n8n and favorite templates
Workflow Visualization
Loading...
Preparing workflow renderer
Comments (0)
Login to post comments