---
name: linkedin-n8n-integration
description: Connect LinkedIn Sales Navigator and n8n: what syncs, which editions carry it, the setup order, and the failures to expect. Covers messages. Use when the user wants to set up, audit or troubleshoot LinkedIn and n8n together, or asks why data is not moving between them.
---

# LinkedIn Sales Navigator and n8n

> Generated from https://www.reversecontact.com/integrations-hub/linkedin-integrations/linkedin-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 and a LinkedIn app. Company posts need the organisation URN.

**What moves:** messages, one way, into LinkedIn.
**How it is built:** zapier, make or n8n, built on the api. **Effort:** minutes.

## The short version

The smallest node in this directory and the one whose size is the most informative. One resource, one operation, create a post, as a person or as an organisation. That is not n8n being lazy: LinkedIn restricts everything interesting to approved Sales Navigator partners and is not taking new ones, so publishing is all that is available through self-serve permissions. Read this page as a map of what LinkedIn allows rather than as a feature list, and if the job is getting LinkedIn data into a system, the answer is a different provider and no LinkedIn dependency at all.

## Which credential lets you post as what

Rows: The n8n credential type. Columns: What you are posting as. Nothing here costs money on either side: n8n's node is in the free build and all three permissions involved are free to request. What varies is whether you get them by ticking a box or by submitting an app for review.

| The n8n credential type | Yourself, as a member | Your company page, as the organisation |
|---|---|---|
| OAuth2 | self-service | not available |
| Community Management OAuth2 | self-service | only after App Review |

- **self-service.** w_member_social arrives with the Share on LinkedIn product, which LinkedIn lists among the permissions available to all developers without special approval. This is live the same afternoon.
- **not available.** The older OAuth2 credential is documented for older LinkedIn apps and accounts, and n8n directs new apps to Community Management OAuth2. Organisation posting is not part of it.
- **only after App Review.** n8n's Organization Support option requests w_organization_social, and both n8n and LinkedIn state it requires completing the Community Management App Review. It is a submission with a queue behind it, not a scope you enable.

Counted off that grid, of four pairings: two give you self-service, one gives you not available, one gives you only after App Review.

A four-cell grid is unusual on this directory and it is the right size for this pair, because there are only two questions: which credential, and whose voice. The one worth planning around is the bottom right, since a project that assumed company posting was a setting now waits on somebody at LinkedIn reading a form.

## What actually syncs

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

| What | Direction | What that means in practice |
|---|---|---|
| A post as a person | One way, in | Create, with the person name or id, the post text, and a media category when the post carries an image or an article URL. |
| A post as an organisation | One way, in | Same operation with an organisation URN, entered as the bare number rather than the full urn:li:company: form. |
| Anything else LinkedIn exposes | One way, in | The HTTP Request node on the same credential, bounded by the permissions your LinkedIn app holds, which for most accounts is publishing only. |
| Anything out of LinkedIn | One way, out | Nothing. There is no read operation and no trigger node, so a workflow can publish and can never listen. |

## Which field lands where

There is nothing to map. The node has one resource with one operation and four parameters, and the useful content on this page is the list of things that are not there and the documented reason each one is missing.

| In LinkedIn | In n8n | What to know about the match |
|---|---|---|
| Post As | Person or Organization | The only genuine fork in the node. Organization is the half that needs App Review, and the parameter will happily be set before the review is granted. |
| Person Name or ID | An identifier for the member | Covered by w_member_social, which LinkedIn lists as an open permission: post, comment and like on behalf of an authenticated member. |
| Organization URN | The organisation number, bare | 03262013 rather than urn:li:company:03262013, in n8n's own example. The full form is what the rest of LinkedIn shows you. |
| Text | The post contents | The whole payload. There is no scheduling parameter, so a posting time is a Schedule Trigger in the workflow rather than a field here. |
| Media Category | For images or article URLs | Used when the post carries media rather than being a parameter you always set. Plain text posts leave it alone. |
| Anything else LinkedIn exposes | HTTP Request node, same credential | The documented escape hatch, and the narrowest one in this directory: it reaches only what your app is approved for, which for a self-service app is publishing. |
| Sales Navigator data | Not available without partnership | r_sales_nav_profiles, r_sales_nav_display, r_sales_nav_validation and r_sales_nav_analytics all require approval as a Sales Navigator Application Platform partner. |
| Lead Gen Form submissions | r_marketing_leadgen_automation, applied for separately | n8n names the scope for its Lead Sync setup and states it needs separate Lead Sync API access. It is not part of the two self-service products. |

### What LinkedIn will and will not let a self-service app do

| The action | How it reads on the record |
|---|---|
| profile | Open. The authenticated member's name, headline and photo |
| email | Open. The authenticated member's primary email address |
| w_member_social | Open. Post, comment and like on behalf of the authenticated member |
| w_organization_social | Community Management App Review, which is a submission rather than a setting |
| The Advertising API permissions | Approval as an advertising partner, applied for through the Developer Portal |
| The four Sales Navigator permissions | Approval as a SNAP partner |

**What does not cross:**

- Any read of another member. The three open permissions describe the authenticated member only, which is why no self-service app can turn a profile URL into a person.
- Any event. There is no trigger node and LinkedIn exposes no webhook through these permissions, so nothing on LinkedIn can start a workflow.
- Comments and likes at scale, even though w_member_social permits them. The node has no operation for either, so they go through raw HTTP and into the rate limits you cannot see.

## Connect it, in this order

**Who has to do it:** Whoever runs n8n, plus an admin on the LinkedIn Company Page you want to post as. The page is a prerequisite rather than an option.
**How long:** Half an hour to post as yourself. Weeks if you need to post as the organisation, because that waits on a LinkedIn review.

### 1. Decide whether you are posting as a person or as a page

*Where:* Design, before the developer portal

Posting as yourself uses an open permission and is live the same afternoon. Posting as an organisation requests w_organization_social, and n8n states plainly that it requires LinkedIn's Community Management App Review. That is the whole difficulty of this pair in one decision.

### 2. Create the developer app against a Company Page

*Where:* LinkedIn Developer Portal: create app

A LinkedIn account is not enough: the app has to be associated with a Company Page, and you can create one during this step if you do not have it. Add a logo, accept the legal agreement, and create the app.

### 3. Request the products rather than hunting for scopes

*Where:* LinkedIn: the app's Products tab

Share on LinkedIn and Sign In with LinkedIn using OpenID Connect are the two self-service products, and they carry w_member_social, profile and email. Add the Advertising API only if you are acting as an organisation. These are the permissions LinkedIn calls open, and they are the only ones available without approval.

### 4. Pick the credential type that matches your app's age

*Where:* n8n: LinkedIn credential

n8n offers Community Management OAuth2 for new accounts and new apps, and plain OAuth2 for older ones. The Legacy option exists to request r_liteprofile and r_emailaddress instead of profile and email, which is for apps created before LinkedIn moved to OpenID Connect.

### 5. Copy the Client ID and the Primary Client Secret

*Where:* LinkedIn: the app's Auth tab

Both go straight into the n8n credential. On n8n Cloud you can use Connect my account and authenticate in the browser instead; self-hosted has to create the developer app either way.

### 6. Enter the organisation URN as a bare number

*Where:* n8n: the LinkedIn node, Organization URN

n8n documents this with an example: 03262013 rather than urn:li:company:03262013. The full form is what LinkedIn shows you everywhere else, which is why this is the most common failure on a node with one operation.

### 7. Look up your own rate limits, because they are not published

*Where:* LinkedIn Developer Portal: the app's Analytics tab

LinkedIn states that standard rate limits are not in the documentation and that the Analytics page shows only endpoints you have called today in UTC. To see a limit for an endpoint that is not listed, make one test call and refresh the page.

### 8. Accept that nothing can start from LinkedIn

*Where:* Design, again

There is no LinkedIn trigger node and no read operation, so a schedule, a webhook from somewhere else, or an approval step has to be what starts the workflow. Any architecture that begins with a LinkedIn event has to be redesigned rather than debugged.

Two of those eight steps are decisions you cannot undo cheaply, and both are at the top. The organisation question gates the project on a LinkedIn review, and the absence of a trigger gates the design. Everything after that is twenty minutes, which is why this sits in the [prospecting layer](layer:prospect) as a publishing tool rather than a data one.

## How to check it worked

- Post once as a person before requesting anything else. If that works, the credential is correct and every remaining problem is a permission rather than a configuration.
- Post once as the organisation with the bare number in the URN field. The failure mode for the full urn:li:company: form does not mention the format, so prove this before building on it.
- Make one call to each endpoint you plan to use, then open the app's Analytics tab. That is the only documented way to see your own limits, and it has to be done inside the same UTC day.
- Check who receives the Developer Admin email alerts. They fire at 75% of quota, only on application-level breaches, and one to two hours late, so the person who gets them needs to be somebody who will act.

## 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 |
|---|---|---|
| The organisation post fails and the error says nothing about the URN | The full urn:li:company:03262013 form was entered where n8n documents the bare number 03262013. | Strip it to the number. Test this on its own rather than inside a workflow, because it is the single most likely cause of a failing organisation post. |
| Posting as the organisation is refused although the scope is ticked | w_organization_social needs LinkedIn's Community Management App Review completed. Requesting the scope and passing the review are two different things. | Submit the review, and post as a member in the meantime. There is no configuration that substitutes for it. |
| The app cannot be created at all | A LinkedIn Company Page is a prerequisite for a developer app, not an optional association. | Create the page during app creation, which LinkedIn allows. A personal account with no page cannot complete the step. |
| The credential authorises but the profile call returns nothing | An older app may be issuing r_liteprofile and r_emailaddress where the newer products issue profile and email. The two sets are not interchangeable. | Turn on the Legacy option in the n8n credential for an older app, or recreate the app with Sign In with LinkedIn using OpenID Connect for a new one. |
| 429 responses with no idea what the limit was | LinkedIn does not publish standard rate limits. There are two ceilings, one for the application and one per member per application, and both reset at midnight UTC. | Open the app's Analytics tab in the Developer Portal, which lists limits only for endpoints you have called today in UTC. For an endpoint that is not listed, make one test call and refresh. |
| A 429 arrived although usage looked fine | LinkedIn documents returning 429 in rare cases as infrastructure protection rather than as a quota breach, and says service returns to normal automatically. | Retry with a backoff rather than redesigning. If it persists across a day, it is a quota rather than protection. |
| The quota warning email arrived after the workflow had already failed | Alerts fire at 75% of quota with an expected delay of one to two hours, and only on application-level breaches rather than member-level ones. | Do not use the email as a control. Instrument the workflow's own error branch, because a member-level breach never generates an alert at all. |
| A workflow was supposed to start when something happened on LinkedIn | There is no LinkedIn trigger node and no read operation. Nothing on LinkedIn can start an n8n workflow through the sanctioned route. | Start the workflow from a schedule, a CRM event or a form, and treat LinkedIn as a destination. A design that needs the other direction needs a different data source rather than a different tool. |

## What breaks, from the vendors' own docs

- **One operation, and no trigger.** The node creates posts and does nothing else, and there is no LinkedIn trigger node, so no LinkedIn event can start a workflow. Every design that begins with something happening on LinkedIn has to start somewhere else. That is a hard boundary rather than a gap to work around, and it is worth establishing before anybody sketches an architecture.
- **The organisation URN must be a bare number.** n8n documents entering 03262013 rather than urn:li:company:03262013 for organisation posts. Supplying the full URN is the usual first attempt because it is what LinkedIn shows you elsewhere, and the resulting error does not point at the format.
- **The permissions ceiling is LinkedIn's, not n8n's.** The HTTP Request escape hatch only reaches what your LinkedIn application is approved for. Sales permissions, covering profiles, display, validation and analytics, need Sales Navigator Application Platform approval, and LinkedIn states it is not currently accepting new partners. So the escape hatch is narrower here than on any other node in this directory.
- **Rate limits exist and are not published.** LinkedIn applies limits per endpoint with both application-level and per-member ceilings, resets them at midnight UTC, and does not publish the standard figures. You find yours in the Developer Portal's analytics or by receiving a 429, and the warning email at 75% of quota arrives one to two hours late by LinkedIn's own documentation.

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

### LinkedIn Sales Navigator

- **Base:** `No public API for this workflow`
- **Auth:** CRM Sync is installed as an app, not called as an API.

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

- **CRM Sync requires Sales Navigator Advanced Plus**, not Advanced. The embedded profile card runs on Advanced and syncs nothing.
- **It does not backfill.** Only new and updated data syncs after switch-on; history needs an uninstall and reinstall.
- **Field mappings cannot be customised.** Every supported field syncs or none do.
- **Read your contract before extracting anything from search results.** The constraint is contractual rather than technical, so it does not announce itself when you cross it. An agent must not automate scraping here.

Docs: https://knowledge.hubspot.com/integrations/connect-hubspot-and-linkedin-crm-sync

### 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: LinkedIn node: https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.linkedin
- n8n docs: LinkedIn credentials: https://docs.n8n.io/integrations/builtin/credentials/linkedin
- LinkedIn: getting access to LinkedIn APIs: https://learn.microsoft.com/en-us/linkedin/shared/authentication/getting-access
- LinkedIn: API rate limiting: https://learn.microsoft.com/en-us/linkedin/shared/api-guide/concepts/rate-limits
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/linkedin-integrations/linkedin-n8n-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/linkedin-integrations/linkedin-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.*
