Classify and route email attachments with easybits, Gmail 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 18 nodes and runs on Gmail events. Along the way it connects Gmail, Google Drive, Google Sheets and Slack and 1 more.
How it runs
Trigger: On Gmail events.
- easybits: Classify Document (Easybits Extractor): uses Easybits Extractor
- Merge: merges the data from its input branches
- Merge: merges the data from its input branches
- Merge: merges the data from its input branches
- Merge: merges the data from its input branches
- Merge: merges the data from its input branches
- Merge: merges the data from its input branches
- Route by Document Type (Switch): routes items into 3 branches
- easybits: Extract Invoice (Easybits Extractor): uses Easybits Extractor
- Upload Invoice to Drive (Google Drive): uses Google Drive
…plus 7 more steps. See the full node list below.
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 Extractor: Purchase Orders, easybits: Classify Document, easybits: Extract Invoice).
- Also check Gmail Trigger below v1.4 runs as v1.4 (drafts skipped, max emails per poll).
Nodes used (7)
- Easybits Extractor
@easybits/n8n-nodes-extractor.easybitsExtractor - Gmail Trigger
n8n-nodes-base.gmailTrigger - Switch
n8n-nodes-base.switch - Merge
n8n-nodes-base.merge - Google Drive
n8n-nodes-base.googleDrive - Google Sheets
n8n-nodes-base.googleSheets - Slack
n8n-nodes-base.slack
From the author
What This Workflow Does Receive any business document via email. The attachment is automatically classified (Invoice, Contract, or Purchase Order) using easybits Extractor, then routed down the correct path where a second Extractor pulls out document-specific…