Route and prioritize support emails to Slack channels with easybits
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 9 nodes and runs on Gmail events. Along the way it connects Gmail, Slack and Extractor (community).
How it runs
Trigger: On Gmail events.
- Prepare Email (Code): runs custom JavaScript code
- easybits: Classify & Score Email (Easybits Extractor): uses Easybits Extractor
- Reroute Low Confidence to Other (Edit Fields (Set)): sets 1 field: data.category
- Route by Category (Switch): routes items into 3 branches
- Slack: uses Slack
- Slack: uses Slack
- Slack: uses Slack
- 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: Classify & Score Email).
- Also check Gmail Trigger below v1.4 runs as v1.4 (drafts skipped, max emails per poll).
Nodes used (6)
- Gmail Trigger
n8n-nodes-base.gmailTrigger - Switch
n8n-nodes-base.switch - Slack
n8n-nodes-base.slack - Easybits Extractor
@easybits/n8n-nodes-extractor.easybitsExtractor - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code
From the author
What This Workflow Does Watches your support inbox, classifies every incoming email by category, scores it for priority based on sentiment and urgency signals, and posts a clean summary to the matching Slack channel. Works equally well for English and German…