Skip to main content

n8n CRM Automation: HubSpot, Pipedrive and Salesforce

n8n CRM automation for HubSpot, Pipedrive and Salesforce: credentials, triggers, lead capture without duplicates, deal alerts, weekly reports and API limits.

Founder of IImagined.ai

Published
Jan 15, 2026
Updated
Oct 13, 2026
Reading time
12 min read
Quick answer

n8n has a built-in app node and trigger node for HubSpot, Pipedrive and Salesforce. Connect HubSpot with a service key or OAuth2, Pipedrive with an API token or OAuth2, and Salesforce with OAuth2 or JWT through an External Client App. Build three workflows first: lead capture that updates existing records instead of creating duplicates, an alert when a deal is won, and a weekly report of deals that have gone quiet. HubSpot and Pipedrive triggers are webhooks; the Salesforce Trigger polls. Pace bulk jobs to each CRM's published API limits.

n8n CRM automation works the same way for HubSpot, Pipedrive and Salesforce: a trigger node starts a workflow when a record changes, and an app node reads or writes records. All three CRMs have both nodes built in. The differences that matter are how each one authenticates, whether its trigger is pushed or polled, and how many API calls you are allowed.

Checked on 13 October 2026 against n8n's node and credential docs for HubSpot, Pipedrive and Salesforce, HubSpot's API usage guidelines, Pipedrive's rate limiting and webhooks v2 guides, and Salesforce's supported editions page. This page has no time-saved or revenue figures: an earlier version carried a case study and star ratings that could not be traced to a source, and they are gone.

What does n8n support for each CRM?

Enough to cover most sales operations work without writing an API call. Each app node can also be attached to an AI agent as a tool.

CRMApp node coversTrigger nodeAuthentication in n8n
HubSpotContacts (create/update, search), contact lists, companies, deals, engagements, forms, ticketsWebhook. Company, contact, conversation, deal and ticket events such as created, deleted or property changedService key (recommended) or OAuth2. The trigger needs a developer API key
PipedriveDeals, persons, organizations, leads, activities, notes, files, deal products, productsWebhook. Create, change or delete events on Pipedrive objectsAPI token or OAuth2
SalesforceAccounts, contacts, leads, opportunities, cases, tasks, attachments, custom objects, documents, flows, users, SOQL searchPolling. Created or updated accounts, contacts, leads, opportunities, cases, tasks, users, attachments and custom objectsOAuth2 or JWT, through an External Client App

When an operation is missing, use the HTTP Request node with Authentication set to Predefined Credential Type and pick the same CRM credential. Our guide to n8n API integration covers that route.

Two kinds of CRM trigger
Webhook: HubSpot and Pipedrive
  • The CRM calls n8n when something changes
  • Arrives when the event happens
  • Your n8n instance needs a public HTTPS address
  • The workflow must stay published or events are missed
  • HubSpot allows one webhook at a time
Polling: Salesforce
  • n8n asks Salesforce on a schedule you set
  • Arrives up to one interval late
  • Nothing has to reach n8n from outside
  • Each check is an API call against your org
  • Returns records created or updated since the last check

How do you connect each CRM?

HubSpot

  • Service key (recommended by n8n). In HubSpot, go to Development, then Keys, then Service Keys. Create a key with the scopes you need and paste it into the n8n credential's App Token field. You need super admin or Developer tools access, and n8n notes that service keys are in public beta.
  • OAuth2. On n8n Cloud, select Connect my account. Self-hosted instances need their own HubSpot app, with its App ID, Client ID and Client Secret.
  • Scopes for the node. oauth, forms and tickets, read and write for contacts, companies and deals, schema read for the same three, crm.objects.owners.read and crm.lists.write.
  • Trigger. The HubSpot Trigger uses a developer API key with a HubSpot app: Client ID, Client Secret, Developer API Key and App ID.

HubSpot's regular API keys are deprecated, and private apps created in the HubSpot UI are now legacy, per n8n's HubSpot credential guide.

Pipedrive

  • API token. Copy Your personal API token from Personal Preferences, API tab. If you belong to several companies, switch to the right one first.
  • OAuth2. Needs a Pipedrive developer sandbox account and an app from the Developer Hub, with n8n's OAuth Redirect URL as its callback. The Pipedrive Trigger requires the webhooks:full scope.
  • Protect the trigger. Pipedrive webhooks support HTTP basic auth. Set Incoming Authentication to Basic Auth on the trigger so calls without the username and password are rejected.

Details are in n8n's Pipedrive credential guide. For two-way sync and AI lead scoring in Pipedrive specifically, see our Pipedrive and n8n guide.

Salesforce

  • Check API access. Salesforce's REST API guide lists Enterprise, Performance, Unlimited and Developer editions as having API access by default, with Professional able to add it. Without it, requests fail with API_DISABLED_FOR_ORG. The connecting user also needs the API Enabled permission.
  • Create an External Client App. n8n's Salesforce credential guide says Salesforce is deprecating Connected Apps and recommends External Client Apps for new integrations. Existing Connected Apps still work.
  • OAuth2. Set the callback to https://oauth.n8n.cloud/oauth2/callback on n8n Cloud, or your instance URL plus /rest/oauth2-credential/callback when self-hosted. Add the Full access and refresh_token, offline_access scopes, and choose Production or Sandbox as the Environment Type.
  • JWT. For server-to-server access, upload a certificate to the app, enable the JWT Bearer Flow, and give n8n the Consumer Key as Client ID, the username and the private key.

Workflow 1: capture leads without creating duplicates

Every lead-capture workflow should look the person up before creating anything. Duplicates are cheap to prevent and tedious to merge, and the shape is the same for all three CRMs.

Lead capture that updates instead of duplicating
  1. 01
    Form Trigger or Webhook

    A JSON POST lands under body.

  2. 02
    If: email present

    Send the rest to a review list.

  3. 03
    Edit Fields: normalize

    Trim and lowercase the email.

  4. 04
    CRM lookup or upsert

    Update the match, or create.

  5. 05
    Notify the owner

    Slack or email, with a link to the record.

The normalizing expression, so that "Ana@Example.com " and "ana@example.com" match:

{{ ($json.body.email || '').trim().toLowerCase() }}

Then write to the CRM:

CRMThe n8n step that avoids duplicates
HubSpotContact, Create/Update a contact, with the normalized email. It creates the contact or updates the one that already has that email
PipedrivePerson, Search all persons, on the email. If a person comes back, update it; if not, create one. A Pipedrive lead must be linked to a person or an organization, so create the lead last, with the person ID
SalesforceLead, Upsert, matched against an External ID field that stores the normalized email. Or Get all with a condition on Email before Create. Salesforce leads require Last Name and Company

Set the workflow's error workflow so a failed CRM call alerts you instead of losing the lead; our n8n error handling guide shows how. The receiving end of the form is covered in the webhook trigger guide.

Workflow 2: alert the team when a deal is won

Three nodes in Pipedrive. The only subtle part is making the alert fire once.

Deal won, posted to Slack
  1. 1
    Pipedrive Trigger

    Deal changes, with basic auth on the incoming call.

  2. 2
    If node

    data.status equals won, and previous.status exists.

  3. 3
    Slack node

    One message with the title, value and currency.

Deal won: {{ $json.data.title }} ({{ $json.data.value }} {{ $json.data.currency }})

The second condition is the one that matters. Pipedrive's webhooks v2 send the deal's new state under data and only the fields that changed under previous. Checking that previous.status exists makes the alert fire when the status flips, not on every later edit to a won deal.

What Pipedrive does when n8n does not answer
  1. 10 seconds
    The delivery times out

    A non-2XX response counts as a failure too.

  2. +3, +30, +150 seconds
    Three more attempts

    Four attempts in total for each event.

  3. 10 failed first attempts
    The webhook is banned for 30 minutes

    Events sent during a ban are lost.

  4. 3 days with no success
    Pipedrive deletes the webhook

    Keep the workflow published and n8n online.

Source: Pipedrive webhooks v2 guide, read 13 October 2026

In HubSpot, the same idea uses the HubSpot Trigger's Deal, Property changed event on the deal stage property. In Salesforce, use the Salesforce Trigger's On Opportunity Updated event. That trigger returns only a few default opportunity fields (see getDefaultFields in the node's source), so fetch the record with a Salesforce node before checking StageName or IsWon.

Workflow 3: a weekly report of deals that have gone quiet

A Schedule Trigger every Monday, one query and one Slack message. In Salesforce, the node's Search resource runs a SOQL query:

SELECT Id, Name, StageName, Amount, LastModifiedDate, Owner.Name
FROM Opportunity
WHERE IsClosed = false AND LastModifiedDate < LAST_N_DAYS:14
ORDER BY Amount DESC
LIMIT 50

Then turn the results into a single message with a Code node that runs once for all items:

// One Slack message listing every quiet deal
const lines = $input.all().map(({ json }) =>
  '- ' + json.Name + ' (' + json.StageName + ', ' + (json.Amount ?? 'no amount') + '), owner: ' + (json.Owner?.Name ?? 'unassigned')
);

return [{ json: { text: 'Open deals with no update in 14 days:\n' + lines.join('\n') } }];

Map {{ $json.text }} into a Slack node. In HubSpot, use Deal, Search deals, with a filter on the last-modified date property. In Pipedrive, get the deals and filter on update_time with an If node. Keep reports read-only: a report that also edits deals is harder to trust. The cron expression guide has the Monday schedule.

How do you stay inside each CRM's API limits?

Know the number before you run a bulk job. These are the published limits on 13 October 2026.

CRMBurst limitDaily limitAlso
HubSpotPrivately distributed apps: 100 requests per 10 seconds on Free and Starter, 190 on Professional and Enterprise, per app250,000 a day on Free and Starter, 625,000 on Professional, 1,000,000 on Enterprise, shared across the accountThe CRM Search API has separate limits
Pipedrive20 to 120 requests per 2 seconds with an API token, 80 to 480 with OAuth, by plan. Search: 10 per 2 seconds on every plan30,000 tokens x plan multiplier (Lite 1, Growth 2, Premium 5, Ultimate 7) x seatsA search costs 40 tokens, a list 20, an update 10, a single read 2
SalesforceDepends on your edition and licencesShown in your orgAPI access itself is off in some editions

Sources: HubSpot's API usage guidelines and Pipedrive's rate limiting guide. When Pipedrive's daily budget runs out, requests return 429 until it resets at midnight in the server's timezone, which may not be yours.

In n8n, pace bulk jobs with Loop Over Items and a Wait node, or the HTTP Request node's Batching option, and turn on Retry on Fail for brief 429s. Prefer search and single-record calls over pulling whole lists, and sync only what changed since the last run. In Pipedrive that is also the cheap option: a single read costs 2 tokens where a list costs 20.

How do you avoid sync loops and bad data?

Before a CRM workflow writes to real records
  • n8n runs as its own CRM user, with only the permissions the workflows need
  • Changes made by that user are skipped, so a workflow never reacts to its own writes
  • Each field has one system that is allowed to change it
  • A custom field stores the other system's record ID, so updates are exact
  • Blank values never overwrite existing data
  • Deletes and merges wait for a human approval step
  • An error workflow is published and alerts someone
  • The first run was against a sandbox or a handful of test records

The loop check is easiest in Pipedrive, whose webhook meta block carries the user_id that made the change and a change_source. For approvals, Slack's send and wait operation in n8n pauses the workflow until someone answers.

Can an AI agent work with your CRM?

Yes, because all three nodes work as AI agent tools. An agent can look up a contact, summarize a deal's history or draft a follow-up note. Give it narrow tools: fix the resource and operation, let the model fill only specific fields, prefer search and read operations, and keep an approval step in front of anything that writes. Our n8n and OpenAI guide covers the agent setup.

Next steps

Start with Workflow 1, since it protects the data every other workflow depends on, then add the alert and the report. For the building blocks, see the n8n tutorial for beginners, n8n email sequences and 25 n8n workflow ideas. If you would rather build your own AI product than CRM automations for clients, AI SaaS Builder is our program on building one on Supabase, Next.js and the Claude API.

n8n CRM automation: FAQ

Does n8n integrate with HubSpot, Pipedrive and Salesforce?

Yes. n8n has a built-in app node and a trigger node for each. The HubSpot node covers contacts, contact lists, companies, deals, engagements, forms and tickets. The Pipedrive node covers deals, persons, organizations, leads, activities, notes, files and products. The Salesforce node covers accounts, contacts, leads, opportunities, cases, tasks, custom objects, flows and SOQL queries.

Which HubSpot credential should I use in n8n?

For the HubSpot node, n8n recommends a HubSpot service key, pasted into the credential's App Token field, or OAuth2, which n8n Cloud connects with Connect my account. The HubSpot Trigger node needs a developer API key credential backed by a HubSpot app. HubSpot's old API keys are deprecated, and private apps created in the HubSpot UI are now legacy.

Why can n8n not connect to my Salesforce org?

Check API access first. Salesforce enables it by default in Enterprise, Performance, Unlimited and Developer editions; Professional needs an add-on, and an org without it returns API_DISABLED_FOR_ORG. The connecting user also needs the API Enabled permission. On n8n Cloud, n8n's docs suggest enabling Approve Connected Apps for Non-Admins on the user's profile if the connection fails.

How do I stop n8n creating duplicate CRM contacts?

Normalize the email address, then look up before you create. The HubSpot node has a single Create/Update contact operation that updates the contact with that email if one exists. In Pipedrive, search persons by email and update the match if there is one. In Salesforce, upsert against an External ID field, or check for the email before creating.

Is the n8n Salesforce Trigger real time?

No. It is a polling trigger: it checks Salesforce on the schedule you set and fetches records created or updated since the last check, so an alert arrives up to one interval late. HubSpot and Pipedrive triggers are different, because those two services push events to n8n through webhooks. For instant Salesforce events, have Salesforce call an n8n Webhook node.

Can n8n run when a Pipedrive deal is won?

Yes. A Pipedrive Trigger set to deal changes receives Pipedrive's webhook for every deal update. The payload holds the deal's new state under data and only the fields that changed under previous, so an If node can check that the status is won and that status is among the changed fields, and ignore every later edit to the same deal.

What are the HubSpot API rate limits?

HubSpot's usage guidelines, read on 13 October 2026, give privately distributed apps 100 requests per 10 seconds on Free and Starter and 190 on Professional and Enterprise. The daily caps, shared across the account, are 250,000, 625,000 and 1,000,000 requests. The CRM Search API has its own separate limits.

Free · no card needed

Start with the free Starter Kit.

A unit economics calculator from AI SaaS Builder, plus four more working files.

Starter Kit5 files · free
See All Access: $99/mo →30-day money-back guarantee