HubSpot + n8n: The Complete Integration Playbook for 2026

Why HubSpot Alone Is Not Enough

HubSpot is an excellent CRM and marketing platform. But it has two structural limitations:

1. Workflow actions are gated by plan — many automation features require Professional or Enterprise tiers (£800–£3,200/month)
2. Integrations are limited — HubSpot connects to common tools, but custom or niche integrations need the Operations Hub API, which is expensive

n8n solves both problems. It connects HubSpot's API to anything — for free (self-hosted) or at flat monthly pricing (cloud). You build the logic visually, and your HubSpot data flows wherever it needs to go.

Setting Up the HubSpot Node in n8n

Authentication

1. In HubSpot, go to Settings → Integrations → Private Apps
2. Create a new private app with scopes: crm.objects.contacts.read, crm.objects.deals.read/write, crm.objects.companies.read
3. Copy the access token
4. In n8n, add a HubSpot credential with this token

Basic Operations Available

• Create/update/delete contacts, companies, deals
• Get contact by ID or email
• Search contacts with filters
• Add to lists, update properties
• Create notes and tasks

The 8 HubSpot + n8n Workflows Worth Building

1. Lead Enrichment on Contact Creation

Trigger: HubSpot webhook → new contact created

Flow: Get contact details → call Clearbit API with the email → update HubSpot contact with company size, industry, LinkedIn URL, tech stack → set a custom enrichment_score property.

Why it matters: Reps spend 15–20 minutes manually researching new leads. This does it in 10 seconds.

2. Intelligent Lead Routing

Trigger: HubSpot webhook → deal stage changes to "Qualified"

Flow: Get deal + contact details → check company size and industry against routing rules → assign deal owner based on territory/vertical → send Slack notification to assigned rep → create a task in HubSpot: "Call within 24 hours".

3. Stripe Payment → HubSpot Deal Closed

Trigger: Stripe webhook → payment_intent.succeeded

Flow: Look up customer in HubSpot by email → if deal exists, move it to "Closed Won" → set deal amount from Stripe payment → add a note with transaction ID → trigger onboarding sequence.

4. Automated Client Onboarding Sequence

Trigger: HubSpot deal stage = "Closed Won"

Flow: Create a new contact list "Active Clients" → send welcome email with onboarding doc link → create HubSpot tasks: kickoff call, send questionnaire, 30-day check-in → assign tasks to account manager → post in Slack #new-clients.

5. Re-engagement for Cold Leads

Trigger: Schedule trigger → runs weekly

Flow: Search HubSpot for contacts with last activity > 60 days, lifecycle = "Lead", no open deals → generate personalised re-engagement email using OpenAI (reference their company/industry) → send via email → log send date as a HubSpot property.

Result: 3–8% of cold leads re-engage per campaign, with zero manual effort.

6. Deal Health Score Alert

Trigger: Schedule trigger → runs daily

Flow: Get all open deals in "Proposal Sent" stage older than 14 days → check last email date, last call date, next task date → calculate a health score → if score < 40, send Slack alert to deal owner + create "At risk — follow up" task in HubSpot.

7. Support Ticket → CRM Note Sync

Trigger: Zendesk/Intercom webhook → ticket created

Flow: Find contact in HubSpot by email → create a HubSpot note with ticket ID, subject, and initial message → if customer is on Enterprise plan, notify account manager in Slack → on ticket close, update note with resolution summary.

8. Monthly Revenue Report

Trigger: Schedule trigger → 1st of month, 8am

Flow: Query HubSpot for all deals closed last month → query Stripe for all payments last month → reconcile totals → format as HTML report → send via email to founder/finance.

Tips for Reliable HubSpot + n8n Integrations

Use webhooks over polling — HubSpot webhooks fire in real-time. Polling every X minutes wastes API quota and introduces latency.

Handle rate limits — HubSpot allows 100 API calls per 10 seconds (Professional/Enterprise). Add a Wait node between bulk operations.

Log failures — add an error branch to every workflow. Send failed records to a Google Sheet or Airtable for manual review.

Test with sandbox data — HubSpot offers a developer sandbox account. Use it before running workflows against production contacts.

Building These Workflows

If you want these eight workflows built and running in your HubSpot account, FlareCross delivers them as a scoped project — typically in 2–3 weeks including testing and documentation.