Route inbound enquiries to HubSpot deals with duplicate protection

by Waliid · 0 views · created 2026-09-11 · CRM

What this workflow does

This workflow has 29 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). It uses only n8n's built-in nodes. It also calls api.hubapi.com over HTTP.

How it runs

Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).

1. Load Demo Enquiry (Code): runs custom JavaScript code
2. Configure HubSpot (Edit Fields (Set)): sets 4 fields: hubspot_pipeline_id, hubspot_stage_id, hubspot_owner_id…
3. Normalize Lead Payload (Code): runs custom JavaScript code
4. Validate Inbound Enquiry (Code): runs custom JavaScript code
5. Enquiry Valid? (If): checks a condition and branches into true / false
6. Search Existing Event (HTTP Request): calls api.hubapi.com (POST)
7. Build Final Result (Code): runs custom JavaScript code
8. Classify Event Search Result (Code): runs custom JavaScript code
9. Webhook Triggered? (If): checks a condition and branches into true / false
10. New Source Event? (If): checks a condition and branches into true / false

…plus 17 more steps. See the full node list below.

HTTP calls to: api.hubapi.com

Before you upgrade to n8n 3.0

Nodes used (7)

• Manual Triggern8n-nodes-base.manualTrigger
• Coden8n-nodes-base.code
• Webhookn8n-nodes-base.webhook
• Ifn8n-nodes-base.if
• HTTP Requestn8n-nodes-base.httpRequest
• Respond to Webhookn8n-nodes-base.respondToWebhook
• Edit Fields (Set)n8n-nodes-base.set

From the author

Quick overview This workflow receives inbound lead enquiries (via a demo trigger or a webhook), validates and normalizes the payload, and routes each new event into HubSpot by finding or creating a Contact and creating an associated Deal with duplicate…

View the original on n8n.io → Check your own copy