---
title: "Salesforce and n8n integration: what syncs, and what it needs"
description: "Salesforce and n8n: what moves, in which direction, which plan carries it, and the limits that bite. Verified October 2026."
url: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-n8n-integration
format: markdown twin of the page above, generated at build time
---

New Unlimited plans are here. Fetch, search and enrich without counting credits. [See plans →](https://www.reversecontact.com/integrations-hub//pricing#plans)

Reverse Contact

### Products

Data

People Data

Company Data

Our Data Quality Standard

Delivery methods

API

Webhooks

CSV Enrichment

MCP

CLI

Integrations

### Use cases

[Sales Product](https://www.reversecontact.com/integrations-hub//use-case/sales-products)[Recruiting Product](https://www.reversecontact.com/integrations-hub//use-case/recruiting-products)[Internal Data Teams](https://www.reversecontact.com/integrations-hub//use-case/internal-data-teams)[AI Products](https://www.reversecontact.com/integrations-hub//use-case/data-for-ai)[CRM Enrichment](https://www.reversecontact.com/integrations-hub//use-case/crm-enrichment)

### Features

[Email Finder API](https://www.reversecontact.com/integrations-hub//feature/email-finder-api)[Phone Number Enrichment](https://www.reversecontact.com/integrations-hub//feature/phone-number-enrichment)[People Search API](https://www.reversecontact.com/integrations-hub//feature/people-search-api)[Agentic Search API](https://www.reversecontact.com/integrations-hub//feature/agentic-search-api)[People Lookalike API](https://www.reversecontact.com/integrations-hub//feature/people-lookalike-api)[Company Search API](https://www.reversecontact.com/integrations-hub//feature/company-search-api)[Person Enrichment API](https://www.reversecontact.com/integrations-hub//feature/person-enrichment-api)[Company Enrichment API](https://www.reversecontact.com/integrations-hub//feature/company-enrichment-api)[Person Social Data API](https://www.reversecontact.com/integrations-hub//feature/social-person-api)[Company Social Data API](https://www.reversecontact.com/integrations-hub//feature/social-company-api)

Security

Pricing

Docs

[Log in](https://app.reversecontact.com/auth/login) [Book a demo](https://www.reversecontact.com/contact?utm_source=integrations-directory&utm_medium=referral&utm_campaign=tool-integrations&utm_content=site-header) [Start for free](https://app.reversecontact.com/auth/signup?utm_source=integrations-directory&utm_medium=referral&utm_campaign=tool-integrations&utm_content=site-header)

# Salesforce and n8n

Connected Apps are on the way out, and n8n Cloud needs a permission admins lack by default.

Checked by **Reverse Contact** · Verified 2026-10-11 · No paid placement

## What you have to buy first

An n8n instance, a Salesforce edition with API access, and an External Client App

## What moves

Contacts, Companies, Deals, Tasks, Custom objects, two-way sync.

The node covers more of Salesforce than any other orchestration tool in this directory: accounts, contacts, leads, opportunities, cases, tasks, attachments, documents, users, custom objects, flows you can invoke, and a raw SOQL search that returns everything in one response. The work is all on the Salesforce side and almost none of it is difficult, but two details decide whether the first afternoon is pleasant. Build an External Client App rather than a Connected App, because Salesforce is retiring the latter. And if you are on n8n Cloud, grant the connecting profile Approve Connected Apps for Non-Admins, which is off by default even for administrators.

## What actually syncs

Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.

| What | Direction | What that means in practice |
| --- | --- | --- |
| Leads, contacts and accounts | Both ways | Create, upsert, get, get all, update, delete, add a note, and add a lead to a campaign. |
| Opportunities | Both ways | Create, upsert, get, get all, update, delete and add a note, plus the metadata overview for the object. |
| Cases and tasks | Both ways | Full create, read, update and delete, and a comment on a case. More of the service object than most connectors touch. |
| Custom objects | Both ways | Create, upsert, get, get all, update and delete, with custom fields added through Additional Fields. |
| SOQL | One way, out | The Search resource executes a SOQL query and returns all results in a single response, which is the fastest route to anything the resources do not model. |
| Flows | One way, in | Get all and invoke, so n8n can hand work back to logic that already lives in Salesforce rather than reimplementing it. |

Four of those six rows move in both directions. The two that do not are SOQL and Flows, and those are the rows that decide how you design around this rather than the ones in the brochure.

## Which field lands where

There is no field mapping here, because the node is a client for the Salesforce API rather than a sync. What there is instead is the widest resource list of any orchestration tool in this directory, and one resource that makes the rest of the list optional.

| In Salesforce | In n8n | What to know about the match |
| --- | --- | --- |
| Account | `Create, upsert, get, get all, update, delete, add note, metadata overview` | Upsert is a distinct operation from create, which matters: it is the only one that will not duplicate a record you already have. |
| Contact | `The same eight, plus add lead to a campaign` | The campaign operation appears on both Contact and Lead, which reads like a duplicate and is two different Salesforce calls. |
| Lead | `Create, upsert, get, get all, update, delete, add note, add to campaign` | No convert operation. A lead conversion has to go through the Search resource or the HTTP Request node, which is the one obvious gap on an otherwise complete list. |
| Opportunity | `Create, upsert, get, get all, update, delete, add note, metadata overview` | Stages and amounts are fields rather than operations, so a stage change is an update with the right picklist value in it. |
| Case | `Create, get, get all, update, delete, add comment, metadata overview` | The only Service Cloud object on the node, and the reason some teams run this pair with no sales use case at all. |
| Custom object | `Create, upsert, get, get all, update, delete` | Custom fields are reached through Additional Fields, then Custom Fields in the dropdown. This is the part that makes the node usable against a real org rather than a demo one. |
| Flow | `Get all flows, invoke a flow` | The most underused pair of operations here. Logic that already exists in Salesforce can be called rather than rewritten, which is how this pair avoids duplicating business rules. |
| Search | `Execute a SOQL query, all results in one response` | Anything the resources above do not model. All results in a single response is convenient and is also how a workflow accidentally pulls a hundred thousand records. |

### The four resources people forget the node has

Worth knowing before you write a report against it, because the wording below is what you will be filtering and searching on rather than anything you choose.

| The action | How it reads on the record |
| --- | --- |
| Attachment | Create, delete, get, get all, update, and a metadata overview |
| Document | Upload a document, which is the only operation on that resource |
| Task | Create, delete, get, get all, update, and a metadata overview |
| User | Get and get all, which is how a workflow resolves an owner before it writes one |

### What does not cross

Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.

- Lead conversion. There is no operation for it, so it goes through SOQL and an update, or through the HTTP Request node on the same credential.
- Anything your edition does not include. API access is the gate in front of every operation above, and no orchestration tool can supply it.
- The org's own rules. Validation rules, required fields, duplicate rules and Apex triggers all apply to every write the node makes, exactly as they apply to any other API client.

Every row above travels as a file: eight field mappings, four action rows and three documented exclusions, each one's note, and the three vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.

The Search and Flow resources are the two that change how this pair is designed rather than what it can do: one means the resource list is never the ceiling, and the other means the logic does not have to move out of Salesforce to be automated. Most workflows that end up duplicating a business rule were built without using either.

## The three checkboxes that differ between JWT and OAuth2

Nothing on this pair is gated by an n8n plan: the node, the trigger and the credentials are all in the free, self-hosted build. The configuration is the fork, and it is three checkboxes under OAuth Policies that have to be set opposite ways depending on the credential you chose. Pick one on each side and the grid marks the answer.

| The n8n credential type | Require Secret for Web Server Flow | Require Secret for Refresh Token Flow | Require PKCE Extension |
| --- | --- | --- | --- |
| JWT | Unchecked | Unchecked | Unchecked |
| OAuth2 | Checked | Checked | Checked |

- **Unchecked** — JWT also needs the JWT Bearer Flow enabled and a digital certificate uploaded, and n8n wants your Salesforce username and the contents of the private key file rather than a client secret.
- **Checked** — OAuth2 needs the Authorization Code and Credentials Flow enabled instead, and n8n wants the Consumer Key and Consumer Secret as the Client ID and Client Secret.

Counted off that grid, of six pairings: three give you unchecked, three give you checked. Two rows that are exact opposites is the whole point of showing this as a grid. Neither setup is harder than the other and both are documented clearly, but the page documents them one after the other, so the common failure is to read the first half, start, finish with the second half, and end up with an app that authorises on neither method.

## How to connect Salesforce to n8n

Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.

- **Who has to do it** — A Salesforce admin who can create an External Client App and edit a profile, plus whoever runs n8n. Two people on two teams in most companies.
- **How long it takes** — An hour for OAuth2. Longer for JWT, because a certificate has to exist first.

Design, not a settings page

n8n supports both and their Salesforce-side settings are deliberate opposites. OAuth2 is the shorter path and gives a user-context connection. JWT needs a self-signed certificate and a private key, and gives a connection that does not depend on a browser session.

Salesforce: Setup, App Manager, New External Client App

Salesforce is deprecating Connected Apps in favour of External Client Apps, existing ones keep working, and n8n says to use the new kind for anything new. Enter a name and a contact email, then tick Enable OAuth under API.

Salesforce: the app's Callback URL box

n8n documents http://localhost:1717/OauthRedirect, or your instance URL if you are self-hosting. Salesforce only permits plain HTTP on localhost, so a self-hosted instance on a bare IP address has to be reachable over valid HTTPS with a DNS name behind it before this field can be filled in at all.

Salesforce: Flow Enablement and OAuth Policies

For JWT, enable the JWT Bearer Flow, upload the certificate, and leave Require Secret for Web Server Flow, Require Secret for Refresh Token Flow and Require PKCE all unchecked. For OAuth2, enable the Authorization Code and Credentials Flow and leave all three checked. The grid below is this step.

Salesforce: Manage Consumer Details

The Consumer Key becomes the Client ID in n8n. For OAuth2 the Consumer Secret becomes the Client Secret; for JWT you paste the contents of the private key file instead, along with your Salesforce username. Set Environment Type to Production or Sandbox to match the org you are pointing at.

Salesforce: Setup, Profiles, Administrative Permissions

Enable Approve Connected Apps for Non-Admins on the profile of the user who will authorise, which may appear as approving apps connected but not installed depending on your language. n8n states it is not enabled by default even for administrator profiles, and without it authentication fails.

Salesforce: Manage Connected Apps, Edit Policies

Salesforce recommends expiring the refresh token after 90 days, a session timeout of 15 minutes, and Permitted Users set to admin approved users are pre-authorized. None is required to connect and all three change what happens three months later.

n8n: the Flow resource

The node can list and invoke Salesforce flows, so logic that belongs in the org can stay there and be called. Deciding this up front is what stops the same rule existing in two places, which is the failure this pair produces most often.

Seven of those eight steps are in Salesforce and one is in n8n, which is the honest ratio for this pair. The grid below covers the one step that is a genuine fork rather than a form to fill in, and the [Salesforce data layer](https://www.reversecontact.com/integrations-hub/workflows/salesforce-data-layer) is where the last step is argued out properly.

Hand it to an agent instead

The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at [this pair as a skill](https://www.reversecontact.com/integrations-hub/skills/salesforce-n8n.md) and it has the whole pair without reading two sets of vendor docs first.

curl -o .claude/skills/salesforce-n8n/SKILL.md https://www.reversecontact.com/integrations-hub/skills/salesforce-n8n.md

## What breaks, and what nobody tells you

Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.

- **Connected Apps are deprecated** — Salesforce is moving to External Client Apps and n8n recommends them for new integrations. Existing Connected Apps keep working and new ones should not be created. Pre-authorising profiles and permission sets is still a step on the legacy path, which is one more reason to take the new one.
- **A permission admins do not have by default** — On n8n Cloud, the connecting user's profile needs Approve Connected Apps for Non-Admins. n8n documents that this is not enabled by default even for administrator profiles. The failure arrives as a refusal to authorise with nothing useful in the message, and it is the first thing to check before anybody rebuilds the credential.
- **The two auth methods have opposite settings** — JWT wants the secret and PKCE requirements turned off under OAuth Policies and a certificate uploaded; OAuth2 wants both requirements left on. Both need the Full access and refresh token scopes and a callback URL that differs between self-hosted and n8n Cloud. Read the half of the page that matches your choice, because following both produces a configuration that authorises on neither.
- **The API allocation is shared and finite** — Salesforce allows 100,000 requests plus 1,000 per Salesforce licence per 24 hours on Enterprise and on Professional with API access, 5,000 per licence on Unlimited and Performance, across every integration in the org. A workflow looping row by row is competing with your existing connectors, and there is a separate cap of 25 concurrent requests running 20 seconds or longer in production.

Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.

## The 8 failures people actually hit

Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.

### Authentication fails from n8n Cloud with nothing useful in the message

WhyThe connecting user's profile is missing Approve Connected Apps for Non-Admins. n8n states this is not enabled by default even for administrator profiles.

Enable it under Administrative Permissions on that profile. It may be labelled as approving apps connected but not installed, depending on your org's language.

### External client app is not installed in this org

WhyAn External Client App has a distribution state. One created as Local can only be used in the org that created it, so the same OAuth flow that works internally refuses for anybody else.

For an app other orgs will use, either authorise with a user holding the approval permission, or package the app and have each org install it. Practitioners report sandbox profiles missing the permission even on standard System Administrator, which Salesforce resolved by matching sandbox licences to production.

### The callback URL will not save, or the redirect 404s

WhySalesforce permits plain HTTP only on localhost. A self-hosted instance on a dedicated IP address has to use HTTPS, and a free certificate needs a DNS name rather than an address.

Put a DNS name and a valid certificate in front of the instance before filling in the callback URL. This is a hosting job rather than a Salesforce one, and it is where the setup stalls on a locked-down network.

### The credential authorises and stops working months later

WhyThe refresh token policy expired it. Salesforce recommends expiring refresh tokens after 90 days, which is advice rather than a default, so somebody probably took it.

Check Edit Policies on the app before blaming the credential. The same page holds the session timeout and the permitted users setting, and all three were set once by somebody who has moved on.

### A write failed and the workflow reported success

WhyValidation rules, required fields, duplicate rules or an Apex trigger rejected the record. The node is an API client and the org refuses it the same way it refuses any other.

Read the node's error output rather than the execution status, and rehearse against a sandbox with Environment Type set to match. Upsert rather than create is also what stops a retry producing a second record.

### A SOQL search returned far more than expected and the workflow stalled

WhyThe Search resource returns all results in a single response by design. There is no paging to protect you from a query without a LIMIT clause.

Put the LIMIT in the query. Salesforce also caps concurrent long-running requests, at 25 running 20 seconds or longer in production, which is what a few of these at once will hit.

### Nothing the workflow needs is in the resource list

WhyLead conversion and anything newer than the node are not modelled. That is the documented scope of it rather than a bug.

Use the Search resource for reads and the HTTP Request node for writes, selecting Predefined Credential Type and the Salesforce credential you already made. No second authentication is involved.

### Someone else's integration started returning errors after your backfill

WhyThe API allocation is shared across the org: 100,000 requests plus 1,000 per licence per 24 hours on Enterprise and on Professional with API access, and 5,000 per licence on Unlimited and Performance.

Batch the reads, use SOQL rather than a loop of gets, and schedule a backfill outside business hours. This is the most socially expensive failure on the page because the symptom appears on somebody else's system.

If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The [same symptom on another pair](https://www.reversecontact.com/integrations-hub/errors) is often the same cause, so the directory indexes all of them by the message rather than by the integration.

## When this is the right integration

### Set it up when

- Logic that an AppExchange package will never cover
- A Salesforce flow needs something only an outside API can answer
- Volume makes per-task pricing more expensive than a server

### Do not bother when

- There is no Salesforce admin time for an External Client App
- Nobody will own the instance once it is built
- Your edition has no API access, which no tool here can fix

The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.

## What practitioners say about it

Searched for this pair by name, in the words a person would use. 14 threads from 2025 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.

### The callback URL is the step that stops a locked-down instance

> I installed n8n on a server which is only accessible behind our firewall by connecting to my vpn. We have a dedicated IP for it but because it is behind our firewall we have no https. \[...\] SF only allows http on localhost, if you enter a dedicated IP it has to be httpS.

[r/n8n](https://www.reddit.com/r/n8n/comments/1jh5hkb/using_n8n_behind_a_firewall_connecting_to/) · March 2025 · 1 points

A correct reading of the constraint, arrived at the hard way. The answer in the thread is a static IP, a DNS name and a certificate, and it notes a free Let's Encrypt certificate needs DNS rather than an address. That is the step before any of the setup list above can begin.

### The permission that blocks authorisation is new and not always granted

> In response to the recent data breaches, Salesforce now added a new permission called "Approve Uninstalled Connected Apps" If no metadata representing the connected app or ECA has been deployed/installed to the org and the user running through the OAuth2 flow does \*not\* have that permission-then they will be blocked, as you've seen.

[r/salesforce](https://www.reddit.com/r/salesforce/comments/1otmk17/pushing_data_to_salesforce_new_integration/) · November 2025 · 1 points

The same permission n8n documents for n8n Cloud, explained from the Salesforce side with the reason it exists. Later in the thread somebody reports standard System Administrator profiles in sandboxes missing it anyway, which Salesforce support resolved by matching the sandbox licences to production.

### The objection in r/salesforce is compliance, not capability

> I love n8n - it's like flows but better. We're a HIPAA org tho so we only get to use it for non-PHI use cases...

[r/salesforce](https://www.reddit.com/r/salesforce/comments/1l9w37h/whats_the_consensus_on_using_thirdparty_ai_agent/) · June 2025 · 7 points

The highest-scoring comment in the set, and it is a scoping decision rather than a complaint. Another in the same thread makes the sharper version of the point: sending inbound case and customer information to an outside model has implications, whatever the workflow looks like.

### It is a batch tool, and the concurrency limit is where that shows

> n8n is a decent workflow tool for batch processes. I find it helpful for prototyping, but I would use it to solve different problems than agentforce. Like you wouldn't be able to use it for customer support on your website, you'd hit the concurrent execution limit pretty fast.

[r/salesforce](https://www.reddit.com/r/salesforce/comments/1l9w37h/whats_the_consensus_on_using_thirdparty_ai_agent/) · June 2025 · 3 points

A useful boundary from somebody who uses both. It lines up with Salesforce's own cap on concurrent long-running requests, and it is the reason the useFor list on this page is about enrichment and backfills rather than anything a customer is waiting on.

### The reason people reach for it is not having to buy more Salesforce

> Not all, but some of the advantages 1. Freedom to deep personalize LLMs/agents 2. Similar yet (much) more powerful automations 3. Not need to buy and set up a dozen Salesforce product for a use case working.

[r/n8n](https://www.reddit.com/r/n8n/comments/1iae6oq/use_case_help/) · January 2025 · 1 points

Written by somebody describing ten years in the Salesforce ecosystem and six as an architect. The third point is the commercial argument this whole layer rests on, and it is the same one the HubSpot pairs make about Data Hub, with a different product name in it.

What the threads add up to

In r/n8n the threads are specific and the problem is almost always authentication, usually the callback URL on a self-hosted instance that has no public HTTPS. In r/salesforce the conversation is about something else entirely: whether this is allowed. The objections are compliance and data residency rather than capability, and they come from people who like the tool. Both are worth reading, because the second set decides whether the first set matters at you.

The two authentication quotes describe behaviour both vendors document, which is what makes them worth printing. The compliance ones are judgements rather than facts, and they are the ones to take to your own legal team rather than to a settings page, because no part of [the orchestration layer](https://www.reversecontact.com/integrations-hub/stack/orchestration) answers them.

## The longer answer

Everything on this page assumes an edition with API access, which is the first gate on every Salesforce pair in this directory and the one that ends the most evaluations. Enterprise and Unlimited include the calls; Professional needs the API add-on enabled; other vendors integrating over the same REST API document Essentials as having none even with an add-on. No orchestration tool changes that, because they are all using the API you either have or do not.

Past that, the choice between n8n and an AppExchange package is the usual orchestration trade in sharper form. A managed package is maintained by its vendor, shaped by their roadmap and installed by your admin in a change window. An n8n workflow is shaped by you, maintained by you, and in version control if you want it there. Salesforce makes the second option more attractive than most CRMs do, because the admin queue in front of a package install is often longer than the build itself, which is the pattern [the Salesforce data layer](https://www.reversecontact.com/integrations-hub/workflows/salesforce-data-layer) is built around.

The detail worth internalising before you start is that n8n can invoke Salesforce flows. That turns the usual argument about where business logic should live into something less absolute: logic that belongs in Salesforce stays in Salesforce and gets called, while the parts Salesforce genuinely cannot do, reaching a third-party API mid-process, branching on something outside the org, run in n8n. Teams that use that split end up with far less duplicated logic than teams that treat the two as rivals.

## If this is not the one

The integrations people compare this against, or set up alongside it.

Split a stack into layers and this pair sits on two of them: the [CRM layer](https://www.reversecontact.com/integrations-hub/stack/crm), which 33 of the 68 integrations here touch, and the [orchestration layer](https://www.reversecontact.com/integrations-hub/stack/orchestration), which 23 do.

[**HubSpot and Salesforce**Two CRMs, one connector, and an edition requirement on both sides. Two-way sync](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-salesforce-integration)[**HubSpot and n8n**The cheapest way out of the Data Hub trap, and the trigger needs a public app. Two-way sync](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-n8n-integration)[**Salesforce and LinkedIn**The original CRM Sync target, with the same Advanced Plus gate. Two-way sync](https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-linkedin-integration)

## [Reverse Contact](https://www.reversecontact.com)

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. [What has changed since](https://www.reversecontact.com/integrations-hub/changes) · [How we checked](https://www.reversecontact.com/integrations-hub/methodology), and what we will not claim

[Eugene Suslov](https://www.linkedin.com/in/eysuslov/)

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

- **Verified** — 2026-10-11
- **Sources** — 3 vendor documents
- **Paid placement** — None

### Read from

- [n8n docs: Salesforce node](https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.salesforce)
- [n8n docs: Salesforce credentials](https://docs.n8n.io/integrations/builtin/credentials/salesforce)
- [Salesforce developer limits and allocations quick reference (PDF)](https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/salesforce_app_limits_cheatsheet.pdf)

## Salesforce and n8n, asked and answered

### How does n8n connect to Salesforce?

Through OAuth2 or a JWT bearer flow, both of which work with the Salesforce node and the Salesforce Trigger. On the Salesforce side you create an External Client App, add the Full access and refresh token scopes, and copy the consumer key into n8n. JWT additionally wants a certificate uploaded and the secret and PKCE requirements turned off; OAuth2 wants them left on. The two setups are deliberate opposites and following the wrong half of the documentation is the usual reason a connection refuses to authorise.

### Why does the connection fail on n8n Cloud?

Most often a Salesforce permission that is not enabled by default even on administrator profiles. n8n documents that connections can fail unless the user's profile has Approve Connected Apps for Non-Admins, sometimes shown as approving apps connected but not installed. It is a one-line fix on the profile and it is almost impossible to guess from the error.

### Should I use a Connected App or an External Client App?

An External Client App. Salesforce is deprecating Connected Apps in favour of them, existing ones keep working, and n8n recommends External Client Apps for new integrations. Building a new automation on a deprecated app type in 2026 is choosing a migration you could have skipped.

### Is this cheaper than an AppExchange connector?

Usually, and the comparison is not really about licence cost. Zapier charges per task and makes Salesforce a premium app, so a paid plan is mandatory there. Self-hosted n8n costs the instance and nothing per execution. What you take on instead is the host, the credentials and the upgrades, and the Salesforce API allocation is spent either way.

Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.

Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.

Ask an assistant
