Catch failed invoice extractions with easybits, Slack, and Google Drive
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 6 nodes and runs on Gmail events. Along the way it connects Slack, Google Drive, Gmail and Extractor (community).
How it runs
Trigger: On Gmail events.
- easybits: Extract Invoice Number (Easybits Extractor): uses Easybits Extractor
- Merge: merges the data from its input branches
- Validate: Invoice Number Present (If): checks a condition and branches into true / false
- Upload to Invoice Folder (Google Drive): uses Google Drive
- Slack: uses Slack
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @easybits/n8n-nodes-extractor is verified or supports 3.0 (used in easybits: Extract Invoice Number).
- Also check Gmail Trigger below v1.4 runs as v1.4 (drafts skipped, max emails per poll).
Nodes used (6)
- Easybits Extractor
@easybits/n8n-nodes-extractor.easybitsExtractor - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack - Google Drive
n8n-nodes-base.googleDrive - Gmail Trigger
n8n-nodes-base.gmailTrigger - Merge
n8n-nodes-base.merge
From the author
What This Workflow Does Monitors incoming invoice emails and catches extraction failures before they slip through. When easybits Extractor can't extract the invoice number from an attachment, the workflow sends a Slack alert to finance so nothing gets lost.…