Skip to main content

Error handling: Send email via Gmail on execution or trigger-level errors

Workflow preview

Workflow preview
100%
Error handling: Send email via Gmail on execution or trigger-level errors preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This error handling workflow emails detailed notifications on workflow execution and trigger errors. It extends [Send email via Gmail on workflow error](https://n8n.io/workflows/696 send email via ...

Best for

  • DevOps automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.errortrigger, n8n-nodes-base.gmail, n8n-nodes-base.merge, n8n-nodes-base.set, n8n-nodes-base.if, n8n-nodes-base.html, n8n-nodes-base.code, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Olek.

Original n8n.io source

1.1 Workflow description

Title
Error handling: Send email via Gmail on execution or trigger-level errors
Workflow name
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


Author

  • Reach out Olek on community.n8n.io
  • Olek on n8n creators hub

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - Error Trigger

Type / Role
n8n-nodes-base.errorTrigger - errorTrigger
Config choices
Version 1

Block 2 - Gmail

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 3 - Merge

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3

Block 4 - Config

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 5 - Constants

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 6 - If

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 7 - HTML for Execution Error

Type / Role
n8n-nodes-base.html - html
Config choices
Version 1.2

Block 8 - HTML for Trigger Error

Type / Role
n8n-nodes-base.html - html
Config choices
Version 1.2

Block 9 - KeepEitherOfHTMLs

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3

Block 10 - Code

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 11 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 12 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 13 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Error handling: Send email via Gmail on execution or trigger-level errors
Complexity intermediate
Nodes 13
Categories DevOps
Author Olek
Published 03 Mar 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/3075/3075.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Frequently asked questions

What does Error handling: Send email via Gmail on execution or trigger-level errors do?

This error handling workflow emails detailed notifications on workflow execution and trigger errors. It extends [Send email via Gmail on workflow error](https://n8n.io/workflows/696 send email via ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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 DevOps use case.