Verify HubSpot contacts with NeverBounce and send risky-email alerts to Slack
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 a schedule (every day). Along the way it connects Slack, HubSpot and Neverbounce Email Verification (community).
How it runs
Trigger: On a schedule (every day).
- Get many contacts (HubSpot): get many
- Loop Through Contacts (Loop Over Items (Split in Batches)): loops over the items in batches
- Slack: uses Slack
- Email Parser (Edit Fields (Set)): sets or maps fields
- NeverBounce: Verify Email (Nb Email Verification): uses Nb Email Verification
- Status Parser (Edit Fields (Set)): sets or maps fields
- Check if risky (Switch): routes items into 2 branches
- HubSpot: uses HubSpot
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 n8n-nodes-neverbounce-email-verification is verified or supports 3.0 (used in NeverBounce: Verify Email).
Nodes used (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Nb Email Verification
n8n-nodes-neverbounce-email-verification.nbEmailVerification - Slack
n8n-nodes-base.slack - HubSpot
n8n-nodes-base.hubspot - Edit Fields (Set)
n8n-nodes-base.set - Switch
n8n-nodes-base.switch
From the author
How it works Use this workflow to regularly re-check contacts from HubSpot and notify your team in Slack when risky records are found. This ensures your CRM stays clean and your sender reputation remains protected. Workflow Logic Scheduled Trigger → Get Many…