n8n Workflow: Route Inbound Leads to HubSpot Deals (Duplicate Proof)

Route inbound leads to HubSpot Deals—without duplicate spam

This n8n workflow receives inbound lead enquiries (via a test trigger or webhook), normalizes and validates the payload, then routes each new event into HubSpot by creating (or finding) a Contact and creating a corresponding HubSpot Deal with duplicate protection and delivery/SLA status fields.

What this workflow does

• Receives lead data from a manual test trigger (or a disabled POST webhook) containing an inbound lead payload.
• Normalizes and validates inputs (e.g., email/phone, service, message). If required data or configuration is missing, it returns a structured 400/500-style result for invalid payloads or missing setup.
• Prevents duplicates by searching HubSpot Deals using a unique source event key. If the same event was already processed, it returns a no-op result.
• Finds or handles Contacts by searching HubSpot Contacts using email (or phone when email is missing). If multiple matches are found, it stops for manual review.
• Creates Contacts when needed and, if the write outcome is uncertain, re-searches by identity to safely recover the Contact ID.
• Creates and verifies Deals for the enquiry with pipeline/stage/owner, initializes delivery and SLA properties, associates the Deal to the Contact, and verifies the created Deal by the event key before returning the final result (and webhook response when applicable).

Use cases

• Automatically convert form or demo enquiries into HubSpot Deals with consistent SLA/delivery tracking.
• Ensure each lead submission is processed exactly once using source event key duplicate proof.
• Operational safeguard: pause on ambiguous Contact matching for manual review.

Technical details

• Tech stack / nodes: if, set, code, webhook, and http request (plus a sticky note for guidance).
• Integration: HubSpot via HTTP requests using a HubSpot private app token credential for Deal and Contact search/creation.