---
name: salesforce-n8n-integration
description: Connect Salesforce and n8n: what syncs, which editions carry it, the setup order, and the failures to expect. Covers contacts, companies, deals, tasks, custom objects. Use when the user wants to set up, audit or troubleshoot Salesforce and n8n together, or asks why data is not moving between them.
---

# Salesforce and n8n

> Generated from https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-n8n-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**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, both ways.
**How it is built:** zapier, make or n8n, built on the api. **Effort:** hours.

## The short version

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.

## The three checkboxes that differ between JWT and OAuth2

Rows: The n8n credential type. Columns: Under OAuth Policies in the app. 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.

| 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.

## What actually syncs

Direction is written from Salesforce's point of view: out means out of Salesforce, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| Leads, contacts and accounts | Two-way sync | Create, upsert, get, get all, update, delete, add a note, and add a lead to a campaign. |
| Opportunities | Two-way sync | Create, upsert, get, get all, update, delete and add a note, plus the metadata overview for the object. |
| Cases and tasks | Two-way sync | Full create, read, update and delete, and a comment on a case. More of the service object than most connectors touch. |
| Custom objects | Two-way sync | 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. |

## 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

| 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:**

- 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.

## Connect it, in this order

**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:** An hour for OAuth2. Longer for JWT, because a certificate has to exist first.

### 1. Pick JWT or OAuth2 before you open Salesforce Setup

*Where:* 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.

### 2. Create an External Client App, not a Connected App

*Where:* 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.

### 3. Set the callback URL to something Salesforce will accept

*Where:* 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.

### 4. Enable the right flow and set the three policy checkboxes

*Where:* 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.

### 5. Copy the consumer details into n8n

*Where:* 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.

### 6. Grant the profile permission that is off by default

*Where:* 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.

### 7. Set the policies Salesforce recommends rather than the defaults

*Where:* 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.

### 8. Decide where logic lives before you build anything

*Where:* 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](wf:salesforce-data-layer) is where the last step is argued out properly.

## How to check it worked

- Authorise once and then wait for the token to refresh rather than declaring it done. A connection that authorises and then fails in 90 days is a refresh token policy rather than a credential problem.
- Run the Search resource with a one-line SOQL query before using any of the object resources. It is the cheapest proof that the scopes and the environment type are right.
- Invoke one Salesforce flow from n8n and confirm it ran in the org's own logs. That is the test of whether this pair can hand work back, which is the half most builds skip.
- Check the org's API usage after a full run. The allocation is shared with every other integration, and the way you find out you exhausted it is somebody else's connector failing.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| Authentication fails from n8n Cloud with nothing useful in the message | The 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 | An 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 | Salesforce 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 | The 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 | Validation 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 | The 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 | Lead 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 | The 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. |

## What breaks, from the vendors' own docs

- **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.

## The APIs, if you are building around it instead

### Salesforce

- **Base:** `https://{instance}.my.salesforce.com/services/data/v60.0`
- **Auth:** OAuth 2.0 through a connected app. **API access is an edition feature**: editions without it cannot run any of this.

| Call | Request | What it does |
|---|---|---|
| `PATCH /sobjects/Contact/{id}` | `{ "RC_Title__c": "VP Sales" }` | Update a record. Custom fields carry the __c suffix. |
| `POST /composite/sobjects` | `{ "allOrNone": false, "records": [...] }` | Batch up to 200. `allOrNone: false` so one bad row does not roll back the batch. |
| `GET /query?q=SELECT+Id,Email+FROM+Contact+WHERE+Title=null` | - | SOQL for the filtered slice. |

**Rules that will cost you time if you skip them:**

- **Validation rules, required fields, duplicate rules and Apex triggers all apply to your writes.** A completed run is not a successful write. Read the per-record errors.
- **The daily API allocation is shared across the whole org**, set by edition and licence count. A row-by-row job competes with every other integration; the symptom of exhausting it is other people's integrations failing.
- Test in a sandbox with ten records before production. The rules you will hit were written years ago by somebody who has left.
- Installing anything usually needs Modify Metadata, Download AppExchange Packages and Customize Application. That is an admin on their own schedule.

Docs: https://developer.salesforce.com/docs/apis

### n8n

- **Base:** `Self-hosted or n8n Cloud`
- **Auth:** Credentials are stored in n8n, not in the workflow JSON, so the workflow stays safe to export and review.

| Call | Request | What it does |
|---|---|---|
| `NODE HTTP Request` | `Authentication: Generic > Header Auth. Name: Authorization. Value: Bearer rc_your_api_key` | There is no dedicated Reverse Contact node and you do not need one. Five minutes to configure, and no node update can break it. |
| `NODE HubSpot Trigger` | - | Authenticates with a **developer API key from a HubSpot developer account**, not a private app token, because that is how HubSpot exposes the webhooks API. Free to create, and nobody expects it. |
| `NODE Wait + IF` | - | The polling loop for Reverse Contact's /live endpoints: Wait 5s, GET the webhook id, IF status != succeeded loop back. |

**Rules that will cost you time if you skip them:**

- HubSpot allows **one webhook URL per app**. Route several object types through one subscription and branch inside n8n with a Switch node.
- Self-hosting is usually the reason this route was chosen: records never leave infrastructure you control. Do not quietly move it to a third-party cloud.
- n8n must be reachable by HubSpot for webhook triggers to fire.

Docs: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- 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
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-n8n-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-n8n-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
