Package Information
Available Nodes
Documentation generating…
Documentation
n8n-nodes-linkedin
An n8n community node for LinkedIn with native @mention support — a drop-in alternative to the built-in LinkedIn node that lets mentions, hashtags, and entity links actually render.
⚠️ Beta. This package is in early beta (
0.1.0-beta.x). The API surface may still change. Feedback and issues welcome.
Why this node?
The official n8n LinkedIn node escapes every reserved character in your post text, which destroys mention markup before it reaches LinkedIn. This node preserves it and adds conveniences on top:
- ✅ Native @mentions —
@[Name](urn:li:organization:123)and@[Name](urn:li:person:456)are passed through to LinkedIn intact, so they render as real, clickable mentions. - ✅ Auto-convert LinkedIn URLs to mentions — paste
https://www.linkedin.com/company/acme/and it becomes@[Acme Inc.](urn:li:organization:123)automatically (organizations only — see Limitations). - ✅ Clickable hashtags — plain
#MyTagis left intact for LinkedIn to render as a hashtag, while#inside URLs is escaped so links stay unbroken. - ✅ Follower @mentions by name — write
@[Jane Smith](no URN) and, when posting as an organization, it's resolved against that org's followers (requires the restrictedr_organization_followerspermission). - ✅ More operations — create (text / image / article / video), get, list, and delete posts, plus a generic Custom API Call.
Installation
In a self-hosted n8n instance:
- Settings → Community Nodes → Install.
- Enter
n8n-nodes-linkedin(add@betafor the latest beta) and confirm.
Or install manually in your n8n custom extensions folder:
npm install n8n-nodes-linkedin@beta
After installing, restart n8n. The node appears as LinkedIn (Mentions).
Operations
Post
| Operation | Description |
|---|---|
| Create | Publish a post as a person or organization. Media: None, Article, Image, or Video. |
| Get | Retrieve a single post by URN. |
| Get Many | List an organization's posts (paginated). |
| Delete | Delete a post by URN. |
Custom API Call
Make an arbitrary authorized request to any LinkedIn REST endpoint (method, path, query, body) using your configured credential — handy for endpoints not yet wrapped by the node.
Writing mentions & hashtags
In the post Text field:
| You write | Result |
|---|---|
@[Acme Inc.](urn:li:organization:123) |
Mention, passed through verbatim |
https://www.linkedin.com/company/acme/ |
Auto-resolved to the org mention above (if Auto Convert LinkedIn URL to Mention is on) |
@[Jane Smith] |
Resolved to a follower mention when posting as an organization (needs r_organization_followers) |
#InboxZero |
Clickable hashtag (LinkedIn converts it on publish) |
Everything else in your text is escaped for you, so @, (, # and friends appear literally in the post.
Mentions only render when the bracket text matches the entity's name — organizations require the exact page name (case-sensitive); people can match part of their name. The URL auto-conversion fetches the exact name for you.
Why the escaping matters: LinkedIn parses post text as little text and, if the parse fails, silently falls back to plain text — publishing your mention markup as literal characters. Hand-writing
{hashtag|#|tag}templates (the format LinkedIn stores, not the one it accepts) triggers exactly that. Write#tag; let the node handle the rest.
Credentials
The node offers two authentication options (set per node via the Authentication dropdown):
Standard (LinkedIn OAuth2 API)
For a regular LinkedIn app with Sign In with LinkedIn + Share on LinkedIn products. Posts on behalf of the authenticated member. Toggle Organization Support off if your app has no organization scopes.
Community Management (LinkedIn Community Management OAuth2 API)
For org features — posting as an organization, the URL→mention lookup, listing org posts, and follower @mentions.
Important: LinkedIn's Community Management API must live in its own dedicated app — it cannot be added alongside Sign In/Share products in the same app, and it is only granted to registered legal entities. A Community Management app also includes member posting (
w_member_social), so a single Community Management credential can do everything (personal posts, org posts, lookups). Enable Follower @Mention Lookup on the credential only if your app has been granted the restrictedr_organization_followerspermission, otherwise authorization may fail.
Limitations
- People can't be mentioned from a profile URL. LinkedIn provides no public API to resolve an arbitrary
linkedin.com/in/...URL to a person URN. Org follower @mentions by name are the only supported member-mention path, and only for followers of the posting organization. - Org URL conversion and org posting need a Community Management app (see above). Without it, you can still mention organizations by typing the mention manually in a personal post.
- Reading posts needs Community Management. The Standard credential requests write-only scopes, so Get and Get Many always fail with it. Even with Community Management, only organization posts can be retrieved: reading a person's posts requires
r_member_social, which LinkedIn grants to approved partners only. - Digit-only hashtags don't work. LinkedIn doesn't linkify tags like
#2026, so they're published as literal text. - Video upload uses LinkedIn's multipart Videos API; very large files take proportionally longer.
Development
pnpm install
pnpm build # tsc + copy icons
pnpm lint # eslint (n8n community ruleset)
License
MIT © Maarten De Block
This is an independent community node and is not affiliated with or endorsed by LinkedIn or n8n.