n8n CRM Automation for HubSpot, Pipedrive and Salesforce (2026)

Checked against n8n's HubSpot, Pipedrive and Salesforce node and credential docs, the node source code in n8n 2.41.4, and each vendor's API documentation on October 1, 2026. This update replaces the January 2026 version, whose case study, time savings, revenue figures, rate limits, star ratings and scoring rules we could not verify.

What n8n supports for each CRM

Sources: n8n's HubSpot, Pipedrive and Salesforce node docs, their trigger pages, and the Pipedrive Trigger source. All three app nodes can be connected to the AI Agent node as tools. When an operation is missing, use the HTTP Request node with Authentication set to Predefined Credential Type and pick the same CRM credential.

Connect your CRM

HubSpot

• Service key (recommended by n8n): in HubSpot, go to Development > Keys > 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 HubSpot lists service keys as a public beta.
• OAuth2: on n8n Cloud, select Connect my account. Self-hosted instances need their own HubSpot app with n8n's OAuth Redirect URL.
• Scopes to start with: crm.objects.contacts.read and .write, the same pair for companies and deals, crm.objects.owners.read, crm.lists.write, forms and tickets, plus the matching schema read scopes.
• Trigger: the HubSpot Trigger needs a developer API key credential backed by a HubSpot developer app. HubSpot allows one webhook at a time for it, so publishing a second HubSpot Trigger workflow stops the first.

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 in Pipedrive. If you belong to several companies, switch to the right one first.
• OAuth2: needs a Pipedrive developer sandbox account and a public app with n8n's OAuth Redirect URL as its callback. The Pipedrive Trigger requires the webhooks:full scope.
• Protect the trigger: set Incoming Authentication to Basic Auth on the Pipedrive Trigger. n8n registers the username and password with Pipedrive and rejects calls without them.

Details in n8n's Pipedrive credential guide.

Salesforce

• Check API access. Salesforce's REST API guide says API access is enabled by default in Enterprise, Performance, Unlimited and Developer editions, and Professional Edition can 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. Salesforce is deprecating Connected Apps, and n8n's Salesforce credential guide recommends External Client Apps for new integrations.
• OAuth2: set the app's callback to https://your-n8n-domain/rest/oauth2-credential/callback on self-hosted n8n or https://oauth.n8n.cloud/oauth2/callback on n8n Cloud, add the Full access and refresh_token, offline_access scopes, and choose Production or Sandbox as the Environment Type in n8n.
• JWT: for server-to-server access, upload a certificate to the app, enable the JWT Bearer Flow, and give n8n the Consumer Key, username and private key.

Workflow 1: Capture leads without creating duplicates

Duplicates are the most common CRM automation mistake. Every lead-capture workflow should look up the person before creating anything. The shape is the same for all three CRMs: n8n Form Trigger or Webhook → If (email present) → Edit Fields (normalize) → CRM lookup or upsert → notify the owner.

1. Trigger: an n8n Form Trigger for a hosted form, or a Webhook node your site or ads tool posts to. For a JSON POST, the Webhook node puts the payload under body.
2. If: keep only items where {{ $json.body.email }} is not empty; send the rest to a review list.
3. Edit Fields (Set): add an email field with the expression below, so "Ana@Example.com " and "ana@example.com" match.

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

Then write to the CRM:

Finish with a Slack or email message to the lead owner, and set the workflow's error workflow so a failed CRM call alerts you instead of losing the lead; see our n8n error handling guide.

Workflow 2: Alert the team when a deal is won

This Pipedrive example posts to Slack the moment a deal's status changes to won:

1. Pipedrive Trigger: Action Change, Entity Deal, Incoming Authentication Basic Auth.
2. If: {{ $json.data.status }} is equal to won, and {{ $json.previous.status }} exists.
3. Slack: send a message such as the one below.

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

The second condition matters. Pipedrive's webhooks v2, which n8n's trigger registers by default, send the current deal under data and only the fields that changed under previous. Checking that previous.status exists makes the alert fire once, when the status flips, rather than on every later edit to a won deal. Pipedrive gives each delivery 10 seconds, retries 3 more times after 3, 30 and 150 seconds, and deletes a webhook with no successful deliveries for 3 consecutive days, so keep the workflow published and n8n online.

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. The trigger returns only a few default opportunity fields, such as the ID, amount and probability (see getDefaultFields in the node's source), so fetch the record with a Salesforce node before checking StageName or IsWon. Because that trigger polls, alerts arrive on your polling interval rather than instantly.

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

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

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 in Run Once for All Items mode:

// 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, Deal > Get Many and an If node on update_time. If the query finds nothing, the workflow simply ends. Keep reports read-only: a report that also edits deals is harder to trust.

Stay inside each CRM's API limits

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 Pipedrive's server timezone. 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.

Avoid sync loops and bad data

• Break loops. If n8n updates a record that also has a change trigger, the update fires the trigger again. Skip changes made by your integration user; Pipedrive's webhook meta block includes the user_id and a change_source.
• Pick one source of truth per field. Two-way syncs where both systems can overwrite the same field end in flip-flopping values.
• Store the other system's ID. A custom field holding the matching record ID makes updates exact and lookups cheap.
• Ask before destructive steps. Put Slack's Send and Wait for Response or Gmail's approval operation in front of deletes and merges.
• Use a dedicated integration user with only the permissions the workflows need. In Salesforce, the Integration user license limits integration users to API-only operations.

Let an AI agent work with your CRM

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 with $fromAI(), prefer search and read operations, and keep an approval step in front of anything that writes. Our n8n AI integration guide covers the agent setup.

Next steps

Start with Workflow 1, since it protects the data every other workflow depends on, then add alerts and reports. For the building blocks, see our n8n tutorial for beginners, API integration guide, n8n email sequences and the n8n workflow library. If you would rather build your own AI product than build CRM automations for clients, AI SaaS Builder covers validating an idea, building it on Supabase, Next.js and the Claude API, launching it and charging with Stripe.

n8n CRM automation FAQ