Enforce sales rules of engagement with AgentMail for HubSpot teams
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 49 nodes and runs on a schedule (cron 0 0 * * 0) (plus 3 other triggers). It uses only n8n's built-in nodes. It also calls api.agentmail.to over HTTP.
How it runs
Trigger: On a schedule (cron 0 0 * * 0) (plus 3 other triggers).
- ⚙️ Read Team_Config (Data table): get
- ⚙️ Load Team_Config (Data table): get
- ⚙️ Read Team_Config (sent) (Data table): get
- ⚙️ Read Team_Config (received) (Data table): get
- GET blockLists (HTTP Request): calls an HTTP API
- 🧠 Calculate Hierarchy Blocks (Code): runs custom JavaScript code
- 🧠 Smart Classify & Route (Code): runs custom JavaScript code
- 🧠 Find Expired Entries (Code): runs custom JavaScript code
- Blocks Needed? (If): checks a condition and branches into true / false
- 🔀 Route by Action (Switch): routes items into 2 branches
…plus 35 more steps. See the full node list below.
HTTP calls to: api.agentmail.to
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)
- Data table
n8n-nodes-base.dataTable - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - Manual Trigger
n8n-nodes-base.manualTrigger - Switch
n8n-nodes-base.switch - Webhook
n8n-nodes-base.webhook - If
n8n-nodes-base.if - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
Who’s it for This is for SaaS founders, agency owners, and Sales Ops managers who use HubSpot but are tired of "toe-stepping." If your BDRs are accidentally emailing your AE’s active deals, or Marketing is blasting "Closed Won" accounts with generic…