Integrate Your CRM with n8n and Make: Complete Guide

CRM integration with n8n or Make connects your forms, email, and billing tools so data flows automatically between systems. Instead of copying contact details from a form submission into your CRM, then into your email tool, then logging the interaction manually, you build a workflow once and let it run.

This guide covers the practical side: what CRM integration actually means at a technical level, how to set it up in both n8n and Make, which workflows deliver the most value for small businesses, and what mistakes to avoid.

Affiliate disclosure: Some links in this post are affiliate links. If you sign up through them, Rain Automation may earn a commission at no extra cost to you. We only recommend tools we use ourselves.

What CRM Integration Actually Means

CRM integration connects your customer relationship management tool to other software so contact data, deal updates, and activities sync automatically. Instead of manually copying form submissions into your CRM, a workflow handles it in seconds. The result is fewer errors, faster follow-up, and a complete record in one place.

CRM integration is the process of connecting your customer relationship management tool to other software so they share data automatically. When someone fills out a contact form on your website, that data can flow directly into HubSpot, Pipedrive, Salesforce, or whatever CRM you use, without anyone typing it in manually.

But it goes further than just contact creation. A proper CRM integration can:

• Create or update contacts when form submissions come in
• Move deals between pipeline stages when certain conditions are met
• Send personalized follow-up emails based on CRM data
• Log activities like calls, meetings, and emails automatically
• Sync contact data between your CRM and other tools (email marketing, invoicing, support desk)
• Trigger internal notifications when high-value deals change status

The two most popular tools for building these integrations without writing code are n8n and Make (formerly Integromat). Both use a visual workflow builder where you connect nodes or modules to define how data moves between apps. If you're new to this space, our complete guide to CRM automation covers the fundamentals.

n8n vs. Make for CRM Integration: Side-by-Side Comparison

n8n and Make both build CRM integrations visually without code, but they target different users. n8n is better for technical teams who want to self-host and avoid per-execution costs, while Make is better for non-technical users who want faster setup and a more guided interface.

Both platforms can handle CRM integration, but they're built for different users. Here's a direct comparison across the factors that matter most for CRM workflows:

Category	n8n	Make
Free tier	Self-hosted: unlimited and free. Cloud: trial only.	Free plan available with limited credits
Paid pricing	Cloud starts at $24/mo (2,500 executions)	Core starts at ~$10/mo (credit-based billing since Aug 2025)
Self-host option	Yes, via Docker or npm. No license fees for community edition.	No. Cloud only.
Native CRM connectors	30+ including HubSpot, Pipedrive, Salesforce, Zoho, Freshsales, Copper	40+ including HubSpot, Pipedrive, Salesforce, Zoho, Freshsales, Monday CRM
Learning curve	Moderate. Expression syntax like {{ $json.field }} requires some learning.	Lower. Point-and-click field mapping is more intuitive for beginners.
Best use case	Technical teams who want unlimited self-hosted executions and AI-enriched CRM workflows	Non-technical users who want fast setup and guided configuration
AI capabilities	Built-in nodes for OpenAI, Anthropic, local LLMs. Strong for AI-enriched CRM workflows.	OpenAI module available. Fewer AI integration options overall.
Execution model	1 execution = entire workflow run (regardless of node count)	Credit-based: each module step consumes credits (a 5-step workflow uses more credits per run)
Error handling	Manual error workflow configuration. Powerful but requires setup.	Built-in error routes per module. More visual and beginner-friendly.
Community templates	318+ CRM workflow templates on n8n.io	Thousands of pre-built scenarios in the template gallery

Choose n8n if: You want to self-host to avoid per-execution costs, you plan to add AI enrichment to your CRM workflows, or you need unlimited executions on a budget.

Choose Make if: You want the fastest setup time, you prefer a more guided UI, or you need a wider selection of pre-built templates to start from.

For a deeper breakdown, see our n8n vs. Make for Small Business Automation comparison.

CRM Integration Example 1: HubSpot Lead Capture with n8n

HubSpot is the most popular free CRM for small businesses, and n8n connects to it through a Private App token with full contact and deal API access. This workflow captures website form submissions via webhook, checks for duplicates, creates contacts and deals, then sends confirmation emails and team notifications automatically.

HubSpot's free tier includes API access. Here's how to build a complete lead capture workflow in n8n.

Step 1: Create a HubSpot Private App

HubSpot retired API keys in 2022. You now need a Private App to authenticate:

1. Go to Settings > Integrations > Private Apps in HubSpot
2. Click Create a private app
3. Name it "n8n Integration"
4. Under Scopes, enable: crm.objects.contacts.read, crm.objects.contacts.write, crm.objects.deals.read, crm.objects.deals.write
5. Click Create app and copy the access token

Step 2: Connect n8n to HubSpot

1. In n8n, add a HubSpot node to your workflow
2. Click Create New Credential
3. Select Private App Token
4. Paste your access token and save
5. Test the connection to verify it works

For the full setup including deal creation and lifecycle stage mapping, see our n8n HubSpot integration tutorial. And if you want to see how HubSpot deal automation works at scale (free tier included), the n8n HubSpot deal automation guide covers that end to end.

Step 3: Build the Lead Capture Workflow

Here's the full node sequence for a webhook-triggered lead capture:

1. Webhook node (trigger): Set method to POST. Copy the production URL and point your website form to it. (See the webhook response modes section below for choosing the right response configuration.)
2. IF node (duplicate check): Add a HubSpot Search node before creation. Search contacts by email using {{ $json.email }}. Route to "create" if no match, "update" if found.
3. HubSpot node (create contact): Set Resource to "Contact", Operation to "Create". Map {{ $json.email }} to Email, {{ $json.firstName }} to First Name, {{ $json.phone }} to Phone.
4. HubSpot node (create deal): Set Resource to "Deal", Operation to "Create". Pass the Contact ID from step 3 into the Associations field. Set deal stage to your first pipeline stage.
5. Send Email node: Configure an SMTP or SendGrid node to send a confirmation email to the new lead. Our n8n Send Email node tutorial covers SMTP credentials, HTML templates, and common errors.
6. Slack node (optional): Post a notification to your sales channel with the lead's name, email, and source.

This six-node workflow handles the entire lead intake process. The duplicate check in step 2 prevents creating redundant contacts when someone submits your form more than once.

For a full tutorial with copy-paste workflow JSON, see our n8n CRM integration tutorial for small businesses.

n8n Webhook Response Modes Explained

When your CRM workflow starts with a Webhook node, the "Respond" setting controls when n8n sends an HTTP response back to the caller, and the "Response Data" setting controls what that response contains. Getting these wrong causes silent form failures, timeouts, or missing confirmation data.

This matters for CRM integrations because your website form (or Zapier, or another tool) is waiting for a response from the webhook. If the response takes too long, the form shows an error to the user even though the workflow completed successfully in the background.

Respond Setting: Immediately vs. When Last Node Finishes

The Webhook node's Respond dropdown has three options:

• Immediately (parameter: onReceived, default): n8n sends back a 200 OK right when the webhook receives the request, before any nodes execute. Your form gets an instant response. The workflow continues processing in the background.
• When Last Node Finishes (parameter: lastNode): n8n waits until the entire workflow finishes, then sends back the output of the final node as the HTTP response. Your form doesn't get a response until every CRM lookup, contact creation, and email send completes.
• Using 'Respond to Webhook' Node: Instead of responding at the start or end, you place a dedicated Respond to Webhook node anywhere in your workflow to control exactly when and what data goes back. This gives you the most flexibility for complex branching workflows.

When to use Immediately: Most CRM lead capture workflows. Your website form just needs to know the data was received. The user sees a "thank you" page right away, and the CRM processing happens asynchronously. This is what I use for 90% of client builds.

When to use When Last Node Finishes: When the calling system needs data back from the workflow. For example, if your form needs the newly created HubSpot contact ID to display a personalized confirmation, or if another automation tool is chaining off the webhook response and needs the enriched lead data.

When to use the Respond to Webhook node: When you need to return data from a mid-workflow step (not the last node), or when different branches need to send different responses. For CRM workflows with conditional logic (e.g., returning "existing contact" vs. "new contact created"), this mode is the cleanest approach.

Response Data Options

When using When Last Node Finishes or the Respond to Webhook node, you also control the shape of the response:

• All Incoming Items (parameter: allEntries): Returns an array of all items processed by the last node. Useful when the workflow processes multiple records in a single execution (batch imports, for example).
• First Incoming Item (parameter: firstEntryJson): Returns only the first item's JSON data, unwrapped from the array. Cleaner for single-record workflows like lead capture, where the calling system expects a flat JSON object, not an array.
• Binary (parameter: firstEntryBinary): Returns binary data from the first item (files, images). Rarely used for CRM workflows.
• No Response Body (parameter: noData): Returns an empty 200 response. Behaves like Immediately but waits for the workflow to finish first.

The Webhook Response Decision Matrix

I call this the Webhook Response Decision Matrix because picking the wrong combination of Respond mode and Response Data is the single most common n8n webhook misconfiguration I fix for clients. The matrix has three tiers:

• Tier 1: Fire-and-Forget (Respond: Immediately). The caller gets an instant 200 OK and never sees workflow latency. Use this for any human-facing form submission.
• Tier 2: Sync Data Return (Respond: When Last Node Finishes). The caller waits for the workflow and receives processed data in the response body. Use this when a downstream system needs output from your workflow.
• Tier 3: Branched Response (Respond: Using Respond to Webhook Node). You control exactly when and what goes back, per branch. Use this for conditional logic where different inputs need different responses.

Scenario	Tier	Respond	Response Data	Why
Website form lead capture	1 (Fire-and-Forget)	Immediately	(ignored)	Fast user experience, async processing
Form needs contact ID back	2 (Sync Data Return)	When Last Node Finishes	First Incoming Item	Clean single-object response
Batch CSV import via webhook	2 (Sync Data Return)	When Last Node Finishes	All Incoming Items	Returns all processed records
Health check / ping endpoint	2 (Sync Data Return)	When Last Node Finishes	No Response Body	Confirms workflow ran, no data needed
Conditional response by branch	3 (Branched Response)	Using Respond to Webhook Node	(set per branch)	Different responses per logic path

When should you use Immediately vs. When Last Node Finishes for CRM webhooks? Use Immediately (the default) for any form submission where the user is waiting on the page, because CRM API calls to HubSpot or Pipedrive typically take 2-5 seconds and the form spinner will sit idle the entire time. Only switch to When Last Node Finishes if the calling system needs processed data (like a new contact ID) in the HTTP response body.

Here's the thing: the most common mistake I see is leaving the Respond setting on When Last Node Finishes for a form submission workflow. In one client build, switching the HubSpot webhook from When Last Node Finishes to Immediately reduced average form response time from 4.2 seconds to under 400ms. If your HubSpot API takes 3-4 seconds (which it often does under load), the form spinner sits there while the user wonders if it worked. Switch to Immediately and your conversion rates stay clean.

For a deeper walkthrough of all webhook node settings, including path configuration and authentication options, see our n8n webhook response mode guide.

CRM Integration Example 2: Pipedrive Deal Stage Trigger with n8n

Pipedrive's visual pipeline makes it ideal for stage-based CRM automation in n8n. This workflow triggers whenever a deal moves to a new stage, then routes to different actions (Slack alerts, email sequences, invoicing, or re-engagement drips) based on the destination stage.

Pipedrive's strength is its visual pipeline. This workflow fires whenever a deal moves to a new stage, then takes action based on which stage it moved to.

Step 1: Set Up the Pipedrive Trigger

1. In Pipedrive, go to Personal Preferences > API and copy your API token
2. In n8n, start with a Pipedrive Trigger node
3. Set the event to "Deal Updated"
4. Create a credential with your API token

Step 2: Filter for Stage Changes

1. Add an IF node after the trigger
2. Set the condition to check {{ $json.current.stage_id }} does not equal {{ $json.previous.stage_id }}
3. This filters out deal updates that don't involve a stage change (like editing a deal's title)

Step 3: Route by Stage

1. Add a Switch node to branch based on {{ $json.current.stage_id }}
2. Create outputs for each relevant stage: Qualified, Proposal Sent, Negotiation, Won, Lost
3. On "Qualified": send a Slack notification to the assigned sales rep
4. On "Proposal Sent": trigger an email sequence with proposal follow-up reminders at day 2 and day 5
5. On "Won": update your invoicing tool (Stripe or QuickBooks) to generate an invoice, and move the contact to a "Customer" segment in your email marketing platform
6. On "Lost": add the contact to a re-engagement email drip and log the loss reason

This workflow replaces manual pipeline management. Your team gets notified at the right time, follow-ups happen automatically, and won deals flow straight into billing. We use a version of this for our own deal pipeline automation. For a step-by-step build that covers HubSpot-specific triggers, stale-deal thresholds, and multi-branch alert routing, see the complete breakdown of what a working n8n pipeline alert workflow looks like. To understand which notification trigger types most teams configure incorrectly before they start building, the trigger types teams most often configure wrong covers the three patterns where deal stage alerts break down.

CRM Integration Example 3: HubSpot Contact Sync with Make

Make's OAuth2 flow and visual field mapping make HubSpot lifecycle sync straightforward, even for non-technical teams. This scenario watches for lifecycle stage changes in HubSpot, then routes contacts to the correct email marketing list, nurture sequence, or onboarding workflow based on where they are in your funnel.

Make's OAuth2 flow makes HubSpot connection straightforward. This example keeps your email marketing lists in sync with HubSpot lifecycle stages.

Step 1: Create the Scenario

1. In Make, create a new Scenario
2. Add a HubSpot CRM > Watch Contacts module as the trigger
3. Click Create a connection, then authorize via OAuth2 (Make redirects you to HubSpot)
4. Set the filter to watch for contacts where Lifecycle Stage changed

Step 2: Build the Routing Logic

1. Add a Router module after the HubSpot trigger
2. Create three routes based on the new lifecycle stage value:
   • Subscriber route: Add to your newsletter list in Mailchimp or ConvertKit
   • Marketing Qualified Lead route: Add to a targeted nurture sequence and notify the marketing team via email
   • Customer route: Move to your customer onboarding email sequence and update their record in your invoicing tool

Step 3: Add Error Handling

1. Click the three dots on each module and select Add error handler
2. Choose Resume for non-critical modules (like Slack notifications)
3. Choose Retry for critical modules (like CRM writes), with 3 attempts and 60-second intervals

Make's field mapping is more visual than n8n's. You click on a field and select from available data in previous modules using a dropdown, rather than writing expressions. For teams without a technical lead, this is often the deciding factor. Our email marketing automation guide covers more patterns for syncing CRM data with email platforms.

CRM Integration Example 4: Salesforce Opportunity Sync with n8n

Salesforce closed-won opportunity sync automates the handoff from sales to delivery by pushing deal data into your project management and billing tools. This n8n workflow watches for won opportunities, pulls the full record via the REST API, then creates projects in Asana or Monday and generates Stripe invoices automatically.

Salesforce is common in larger small businesses (10+ person sales teams). This workflow syncs closed-won opportunities from Salesforce to your project management and billing tools.

1. Salesforce Trigger node: Set to watch for Opportunity updates where Stage equals "Closed Won"
2. HTTP Request node: Call the Salesforce REST API to pull the full opportunity record, including associated contacts and line items
3. Set node: Transform Salesforce field names to match your downstream tools (Salesforce uses Amount, your PM tool might need project_budget)
4. Asana/Monday node: Create a new project in your PM tool with the deal name, amount, and primary contact
5. Stripe node: Generate an invoice using the opportunity's line items and amount
6. Gmail node: Send the sales rep a summary email confirming the handoff from sales to delivery

This is more advanced than the HubSpot and Pipedrive examples because Salesforce's API is more complex. The HTTP Request node gives you flexibility when n8n's built-in Salesforce node doesn't cover a specific endpoint. Check our guide on eliminating manual CRM data entry for more on reducing handoff friction.

CRM Integration Example 5: Zoho CRM Lead Scoring with Make

Zoho CRM lead scoring in Make enriches new leads with company data from Apollo.io and assigns a numeric score based on company size, industry fit, and email domain quality. Leads scoring above 70 trigger instant sales alerts, while lower scores route to nurture sequences or low-priority lists automatically.

This Make scenario watches for new Zoho CRM leads and enriches them with company data, then assigns a lead score.

1. Zoho CRM > Watch Records module: Trigger on new Lead records
2. HTTP module: Call the Apollo.io Enrichment API with the lead's email to get company size, industry, and revenue data
3. Set Variable module: Calculate a lead score based on rules you define (e.g., company size > 50 employees = +20 points, industry matches your ICP = +30 points, has a business email domain = +10 points)
4. Zoho CRM > Update Record module: Write the enrichment data and lead score back to the Zoho lead record
5. Router module: If score > 70, send a Slack alert to sales with a "hot lead" tag. If score 40-70, add to nurture sequence. If score < 40, add to low-priority list.

Automated lead scoring replaces the gut-feel approach most small teams use. For more on this pattern with HubSpot instead of Zoho, see our automated lead scoring with n8n and HubSpot tutorial.

Five CRM Workflows Every Small Business Should Build

These five workflow patterns are the highest-value CRM automations for small businesses, and they work in both n8n and Make with any supported CRM. Start with the form-to-CRM contact workflow, then layer on welcome emails, stage notifications, list syncing, and payment-to-deal status updates as your team grows.

Beyond the platform-specific examples above, these five workflow patterns apply universally. They work in both n8n and Make with any supported CRM.

1. Website Form to CRM Contact

Trigger: Form submission via webhook. Action: Create CRM contact with all form fields mapped. This eliminates manual data entry and ensures every lead is captured immediately. Our webhook lead capture guide walks through the n8n setup.

2. New Contact to Welcome Email Sequence

Trigger: New contact created in CRM. Action: Send a personalized welcome email, then schedule follow-up emails at day 3 and day 7. To configure the email step in n8n, our n8n Send Email Node configuration guide covers SMTP credentials, field mapping, and common troubleshooting. First response speed matters. According to InsideSales.com/MIT research cited by HubSpot, responding within 5 minutes makes you 21x more likely to qualify a lead compared to waiting 30 minutes.

3. Deal Stage Change to Team Notification

Trigger: Deal moves to a new stage in your pipeline. Action: Post a message in Slack or send an email to the assigned team member. This keeps your team aligned without anyone needing to check the CRM constantly.

4. CRM Contact Update to Email List Sync

Trigger: Contact properties change (e.g., lifecycle stage, lead score). Action: Add or remove the contact from the appropriate email marketing segment. Our guide on CRM email automation covers best practices for keeping lists in sync.

5. Invoice Payment to CRM Deal Status

Trigger: Payment received in Stripe, QuickBooks, or your invoicing tool. Action: Update the associated deal in your CRM to "Won" and log the payment amount. This closes the loop between billing and sales tracking.

Common CRM Integration Mistakes to Avoid

The most common CRM integration failures come from three areas: syncing too much data, skipping duplicate detection, and not setting up error alerts. After building CRM automations for dozens of small businesses, I can trace almost every lost-lead incident back to one of these root causes.

After setting up CRM integrations for dozens of small businesses, these are the mistakes I see most often.

Syncing Everything

Not every field needs to sync between every tool. Start with the minimum viable data (name, email, deal stage) and add fields as you need them. Over-syncing creates noise and makes debugging harder.

Ignoring Duplicate Detection

Now, this one catches people off guard. If someone submits your contact form twice, your workflow will create two contacts unless you add a check. Always search for existing contacts by email before creating new ones. In n8n, add a CRM Search node before the Create node and route accordingly with an IF node.

Using Test URLs in Production

Both n8n and Make have separate test and production webhook URLs. The test URL only works while you're actively testing in the editor. When you activate your workflow, make sure your forms point to the production URL. And don't forget to set the correct webhook response mode before going live.

Not Handling Errors

CRM APIs have rate limits and occasional downtime. Without error handling, failed operations silently drop data. In n8n, configure an Error Trigger workflow that logs failures and sends you an alert. In Make, use the built-in error route on each module. A client running a 12-person insurance agency lost three weeks of leads last year because their HubSpot token expired and the workflow just silently failed. A simple error notification would have caught it on day one.

Overcomplicating the First Workflow

Start with a simple form-to-CRM workflow. Get it running reliably. Then add enrichment, lead scoring, and multi-step sequences incrementally. Building a 15-node workflow on your first attempt usually results in something that's hard to debug and harder to maintain. Start simple, following the approach in our CRM automation setup guide.

Pricing Comparison for Small Business CRM Automation

CRM automation costs range from $0 (n8n self-hosted on a $10/mo VPS) to $49/month (Zapier Professional), with Make and n8n Cloud falling in between. The right choice depends on whether you prioritize cost control and flexibility (n8n) or faster setup with less maintenance (Make or Zapier).

Here's what it actually costs to run CRM automation at small business scale (100-500 leads per month):

Platform	Plan	Monthly Cost	Execution Limit	Best For
n8n (self-hosted)	Community	$0 + ~$10 VPS	Unlimited	Technical teams, budget-conscious
n8n Cloud	Starter	$24	2,500 executions	Small teams wanting managed hosting
Make	Core	~$10/mo	Credit-based (varies by module complexity)	Non-technical users, faster setup
Make	Pro	~$34/mo	More credits + priority execution	Teams needing priority execution
Zapier	Professional	~$49/mo (annual)	2,000 tasks	Simplest setup, most integrations

Note: Make.com switched from operation-based billing to a credit system in August 2025. Credits consumed vary by module type and complexity. Check make.com/en/pricing for current rates. Zapier pricing reflects the Professional tier as of early 2026.

At 500 leads per month with a 4-step workflow, you'd use roughly 500 executions in n8n (1 execution per lead regardless of node count). Make and Zapier costs scale with the number of steps per workflow. n8n's self-hosted option is the clear winner on cost if you're comfortable with Docker.

For a detailed Zapier comparison, see our n8n vs Zapier for lead capture breakdown. So here's the question worth asking: do you value lower cost and full control, or faster setup and less maintenance? That answer determines your platform.

CRM Integration FAQ: n8n, Make, Pricing, and Webhooks

Can I integrate my CRM with n8n for free?

Yes. n8n's self-hosted community edition is free and supports all CRM integrations, including HubSpot, Pipedrive, Salesforce, and Zoho. You only need a server to run it on, which costs around $5-10/month from providers like Hetzner or DigitalOcean. There are no per-execution fees.

Which is easier to set up, n8n or Make?

Make is generally easier for beginners because its field mapping uses dropdowns instead of expressions. You can build a basic CRM workflow in Make in about 20 minutes. n8n takes a bit longer to learn, but its expression system gives you more flexibility once you're comfortable with it.

Do I need coding skills to integrate my CRM?

No. Both n8n and Make are visual workflow builders designed for non-developers. You connect pre-built nodes or modules by dragging connections between them. That said, some comfort with concepts like APIs, JSON, and webhooks helps when troubleshooting.

How many CRM integrations can I run before hitting cost limits?

On n8n self-hosted, there's no limit. On n8n Cloud Starter ($24/mo), you get 2,500 executions. On Make, costs depend on your credit allocation and the complexity of each module in your scenario. A 5-step workflow processing 500 leads will consume significantly more credits than a 2-step workflow at the same volume.

What happens if my CRM integration breaks?

Without error handling, you lose data silently. Both platforms support error notifications: n8n uses an Error Trigger workflow, and Make uses built-in error routes on each module. Set these up before going live. Check our guide on building automated follow-up sequences for examples of error-resilient workflow design.

What is the difference between the n8n webhook Immediately and When Last Node Finishes response modes?

With Immediately (internally called onReceived), n8n returns an HTTP 200 right when the webhook receives data, then processes the workflow in the background. With When Last Node Finishes (lastNode), n8n waits for the entire workflow to complete and returns the final node's output. Use Immediately for website forms where you want instant user feedback, and When Last Node Finishes when the calling system needs processed data back. A third option, Using Respond to Webhook Node, lets you control response timing from any point in the workflow. Our webhook response modes guide covers all options in detail.

Getting Started

If you're ready to connect your CRM, start with the website form to CRM contact workflow. It takes 30-45 minutes to build, handles the highest-volume use case, and gives you a working foundation to build on. If you want to understand the underlying patterns that make CRM connections work across different tool types, the breakdown of common CRM integration patterns is worth reading before you start wiring nodes.

For a step-by-step tutorial with copy-paste workflow JSON, see our n8n CRM integration tutorial for small businesses.

Need to pick a CRM first? Our guide to choosing a CRM covers the evaluation framework, and our n8n vs. Make comparison helps you pick the right automation platform. For a broader look at CRM automation setup, we cover the full process from choosing tools to going live.

If you'd prefer someone to build and manage your CRM integrations, check out our automation services or get in touch directly. We design custom CRM automation workflows for small businesses using n8n and Make.

Ready to try n8n? Start a free trial or self-host from the n8n GitHub repository.