One resource, one operation: create a post. That is the whole node.
An n8n instance and a LinkedIn app. Company posts need the organisation URN.
Messages, one way, in.
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.
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 |
|---|---|---|
| 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. |
Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.
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. |
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 |
|---|---|
| profile | Open. The authenticated member's name, headline and photo |
| 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 |
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.
Every row above travels as a file: eight field mappings, six action rows and three documented exclusions, each one's note, and the four 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.
Three open permissions against three approval programmes is the real shape of LinkedIn as an integration target, and it explains why this node has one operation while the Salesforce one has sixty. Read it as a map of what is allowed rather than as a feature comparison, and the recommendation on the rest of this page follows from it.
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. Pick one on each side and the grid marks the answer.
Pick one on each side.
| 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 |
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 as a publishing tool rather than a data one.
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 and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/linkedin-n8n/SKILL.md https://www.reversecontact.com/integrations-hub/skills/linkedin-n8n.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
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.
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.
WhyThe 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.
Whyw_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.
WhyA 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.
WhyAn 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.
WhyLinkedIn 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.
WhyLinkedIn 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.
WhyAlerts 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.
WhyThere 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.
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 is often the same cause, so the directory indexes all of them by the message rather than by the integration.
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.
Searched for this pair by name, in the words a person would use. 14 threads from 2023 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.
Look, I gotta be straight with you because this exact workflow gets requested constantly and it's gonna cause you problems. LinkedIn's Terms of Service explicitly prohibit automated profile scraping, especially at the scale you're describing. Sales Navigator is heavily monitored and they will ban your account if they detect bulk automated extraction. Our clients who try this approach usually get flagged within days
r/automation·November 2025·2 points
Answering a Sales Navigator automation request that was cross-posted to five subreddits in one day, which is itself the measurement: this is the most requested thing on the pair and the node does none of it. The commenter sells services in this space, so read the claim about clients accordingly; the terms are a document anybody can check.
This data is not scraped from inside LinkedIn, It uses Google search, so even a non-member of LinkedIn can see it.
r/n8n·June 2025·2 points
The author of a widely upvoted lead-scraping workflow defending its design, and the distinction is a real one rather than a dodge. It is also the reason the next quote matters, because what Google can see is not what the workflow was sold as returning.
If this workflow relies on Google site search, it's likely missing a lot of important detail. Google only indexes surface-level info like name, headline, and recent activity. It doesn't capture experience or other key sections [...] LinkedIn cut that off a while ago.
r/n8n·June 2025·2 points
The two quotes above are from the same thread and they settle the question between them: the sanctioned-looking route exists and returns the fields nobody needed. This is the clearest practitioner statement of why the recommendation on this page is a licensed provider rather than a clever workflow.
You mention spreading requests over 11+ days using n8n Wait nodes. What happens to the queued leads if my self-hosted n8n instance restarts or crashes during that week? Since n8n execution data is usually held in memory or temporary states during a Wait, a server update or crash would kill the workflow, losing all remaining leads in the loop.
r/n8n·January 2026·6 points
The highest-scoring substantive comment in the set and the only one about architecture. It generalises past LinkedIn: any workflow paced over days to stay under a limit you cannot see is holding state in the one place that does not survive a restart.
We tried solving this with some existing tools in the market and have struggled to get good data entry. I think the full automation side (everything "just works") is pretty hard to achieve with LinkedIn because they're extremely anti that.
r/hubspot·January 2026·3 points
From somebody building in the category rather than complaining about it, and their next move is semi-automated: a rep highlights part of the page and it logs. That is the shape of what is left once the sanctioned route is publishing only.
Almost nobody in these threads is using the LinkedIn node. They are using n8n to scrape LinkedIn, and the threads are an argument about whether that works and whether it is allowed. Two answers recur and they are worth reading together: the terms of service prohibit it and accounts get flagged, and the Google-search workaround people reach for instead returns only what Google indexes, which is a headline rather than a profile. The one architectural question in the set is about something else entirely, and it is the best comment of the fourteen.
Four of the five describe the consequences of a permission structure LinkedIn documents, which is why they belong next to that table rather than instead of it. The fifth is about n8n's own durability and is worth taking seriously by anybody building in the orchestration layer, whichever vendor sits at the end of the workflow.
The most valuable thing on this page is the shape of the limit rather than the feature. When a tool as open-ended as n8n, which will happily call any HTTP API you point it at, ships a LinkedIn node with a single operation, the constraint is clearly not the tool. LinkedIn gates its sales permissions behind a partner programme that is closed to new applicants, and the self-serve permissions cover publishing. That single fact explains this node, the Zapier app, and the entire market of browser extensions that exists because the sanctioned route is unavailable.
It also means the usual n8n argument does not apply here. On every other pair in the orchestration layer, choosing n8n buys you the ability to go beyond what the vendor built, because the HTTP Request node reaches the rest of the API. On LinkedIn there is no rest of the API to reach without a partnership. Self-hosting does not help, writing code does not help, and a developer who promises otherwise is describing either a partner programme they are not in or a scraper.
So the honest recommendation is to stop treating this as a LinkedIn integration problem. If the goal is a person and a company behind a profile URL or an email, use a provider that licenses its own data, and let n8n do what it is good at: calling that API, branching on the confidence score, and writing the result into the CRM. That chain has no LinkedIn dependency, no user agreement question and no page layout to break, which is why it is the one in the CRM data layer.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under LinkedIn, n8n and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
It creates posts. One resource, Post, and one operation, Create, publishing as either a person or an organisation with text and an optional media category for images or article links. There is no read operation, no trigger node and no prospecting capability. For anything beyond posting, n8n points you at the HTTP Request node using the same credential, which is only as capable as the permissions your LinkedIn app actually holds.
Because the useful permissions are not available. LinkedIn restricts sales-related API access to approved Sales Navigator Application Platform partners and documents that it is not currently accepting new partners. Only the open permissions are self-serve, and they cover publishing rather than profile or company data. Every orchestration tool in this directory has the same single capability for the same reason.
Choose Organization and supply the URN as a bare number. n8n documents this explicitly: enter 03262013 rather than urn:li:company:03262013. It is the single most common configuration error on this node, it produces an unhelpful failure, and it is one line in the documentation that nobody reads twice.
Not with this node, and not with any sanctioned route unless you are a LinkedIn partner. Teams that need this resolve identity through a provider with its own licensed dataset and let n8n move the result, which is a workflow with no LinkedIn dependency at all. The alternative, a browser extension driving LinkedIn pages, is the category LinkedIn's user agreement prohibits and it is worth being explicit about which one you are choosing.
No. The node has one operation and it creates a post, there is no trigger node, and the three permissions LinkedIn makes available to every developer without approval describe the authenticated member only: their name, headline and photo, their primary email, and posting on their behalf. So nothing can read another member and nothing on LinkedIn can start a workflow. The HTTP Request node reaches only what your LinkedIn app is approved for, which for a self-service app is publishing.
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.