Send daily workflow health digests with the n8n API and Gmail
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 16 nodes and runs on a schedule (every day at 06:00) (plus 1 other trigger). Along the way it connects Gmail.
How it runs
Trigger: On a schedule (every day at 06:00) (plus 1 other trigger).
- Set Configuration Parameters (Edit Fields (Set)): sets 6 fields: alertEmail, scopeTags, instanceUrl…
- Get Published Workflows (n8n): get many (workflow)
- Apply Workflow Scope (Code): runs custom JavaScript code
- Get Recent Error Logs (n8n): get many (execution)
- Identify Scheduled Workflows (Code): runs custom JavaScript code
- Retrieve Last Runs (n8n): get many (execution)
- Verify Missed Schedules (Code): runs custom JavaScript code
- Identify Errored Executions (Code): runs custom JavaScript code
- Detect Silent Failures (Code): runs custom JavaScript code
- Review Sub-workflow Invocations (Code): runs custom JavaScript code
…plus 3 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - n8n
n8n-nodes-base.n8n - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Gmail
n8n-nodes-base.gmail - No Operation, do nothing
n8n-nodes-base.noOp
From the author
Quick overview A daily health check for your n8n instance. Through the n8n API, which it only reads, it looks for failed executions, schedules that didn't fire, workflows with no working failure path, and broken sub-workflow calls, then emails a digest only…