Review and fix HubSpot deal pipeline hygiene with TypeSafe Jev and Gmail
Ready for 3.0What this workflow does
This workflow has 28 nodes and runs on a schedule (every week at 08:00) (plus 1 other trigger). Along the way it connects Gmail. It also calls api.hubapi.com and api.typesafe.ai over HTTP.
How it runs
Trigger: On a schedule (every week at 08:00) (plus 1 other trigger).
- Set HubSpot Parameters (Edit Fields (Set)): sets 9 fields: pipelineId, reviewerEmail, staleDays…
- Send Error Alert Email (Gmail): uses Gmail
- Fetch HubSpot Portal Details (HTTP Request): calls api.hubapi.com
- Fetch HubSpot Pipeline (HTTP Request): calls an HTTP API
- Fetch Pipeline Owners (HTTP Request): calls api.hubapi.com
- Stop if Pipeline Missing (Stop and Error): stops the run with an error
- Post to HubSpot Deals Search (HTTP Request): calls api.hubapi.com (POST)
- Collect Closed-Won Deals (Code): runs custom JavaScript code
- Fetch Won-Deal Companies (HTTP Request): calls api.hubapi.com (POST)
- Extract Client Company IDs (Code): runs custom JavaScript code
…plus 16 more steps. See the full node list below.
Services it uses
HTTP calls to: api.hubapi.com, api.typesafe.ai
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)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Stop and Error
n8n-nodes-base.stopAndError - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Gmail
n8n-nodes-base.gmail - Error Trigger
n8n-nodes-base.errorTrigger
From the author
Quick overview This workflow runs every Monday and scans a HubSpot deal pipeline for hygiene issues and expansion opportunities, optionally using TypeSafe Jev to recommend fixes. It emails a Gmail approval form, then applies only the reviewer-approved updates…