How to Connect n8n to LinkedIn: Built-in Node vs Community Nodes

n8n’s built-in LinkedIn node does one thing: it creates posts, as a person or as an organization. Everything else people want from LinkedIn in their workflows, such as messages, profile and company data, job listings or lead lists, comes from community nodes that connect to third-party LinkedIn services. This guide covers the built-in node and its credentials (from n8n’s documentation), LinkedIn lead forms through the Lead Sync API, and the most used LinkedIn community packages (from our own npm data).

Quick comparison

The built-in LinkedIn node

The only operation is Post > Create. Its parameters:

• Post As: Person or Organization.
• Person Name or ID or Organization URN. For an organization, enter only the number, for example 03262013, not urn:li:company:03262013.
• Text: the post contents.
• Media Category: use it when the post includes images or article URLs.

Set up the LinkedIn credential

You need a LinkedIn account and a LinkedIn Company Page. There are two methods: Community Management OAuth2 for new LinkedIn users and new apps, and OAuth2 only for older apps and accounts. n8n’s docs say the credential works with LinkedIn API version 202404.

Community Management OAuth2

1. While logged in to LinkedIn, create a new developer app and give it a name such as n8n integration.
2. Under LinkedIn Page, enter your Company Page or create one, add an app logo, accept the legal agreement and select Create app.
3. On the Products tab, add Share on LinkedIn and Sign In with LinkedIn using OpenID Connect, plus the Advertising API if you post as an organization rather than an individual.
4. On the Auth tab, copy the Client ID and the Primary Client Secret into the n8n credential.

To post as an organization, your app has to pass LinkedIn’s Community Management App Review.

OAuth2 (older apps)

The legacy method has two switches: Organization Support, which requests the w_organization_social scope to post as an organization (also needs the App Review), and Legacy, which uses the old r_liteprofile and r_emailaddress scopes instead of profile and email. Self-hosted users create their own developer app with the same steps as above.

LinkedIn lead forms in n8n (Lead Sync API)

There is no LinkedIn trigger node, but n8n’s credential docs describe how to receive lead form responses from LinkedIn ads and organic forms with a Webhook trigger and LinkedIn’s Lead Sync API. It needs extra approval from LinkedIn:

1. Link your company LinkedIn account to your developer app and request the Lead Sync API product on the app’s Products tab.
2. Make sure the app has the r_marketing_leadgen_automation permission.
3. Create an n8n workflow with a Webhook trigger. Its URL must be HTTPS, public and accept POST requests without extra authorization.
4. When you register the webhook, LinkedIn sends a GET request with a challengeCode. The workflow must answer within 3 seconds with JSON containing challengeCode and challengeResponse, the HMAC-SHA256 of the code with your app’s Client Secret as the key.
5. Create a subscription with the leadNotifications API (at owner, form or associated entity level), then fetch the leads with the leadFormResponses API.

Lead types are SPONSORED (ads), COMPANY (company pages), EVENT and ORGANIZATION_PRODUCT. LinkedIn re-validates the webhook every 2 hours and blocks it after 3 failed validations in a row, so it must always answer the challenge in time and return a 2xx status. To check that a notification really comes from LinkedIn, compare the X-LI-Signature header with your own HMAC-SHA256 of the JSON body, using the Client Secret, and discard events that don’t match.

LinkedIn community nodes

Our LinkedIn hub lists 26 packages that pass our quality rule, with 63,799 npm downloads a week between them. The most downloaded, with the description each author gives on npm (weekly npm downloads as of 27 October 2026):

Most of these work through an outside service that has its own account, pricing and terms, so read each README before you install. The formatter is the exception: it only turns Markdown into LinkedIn-ready text, which pairs well with the built-in node’s Text field. Check each package’s node page here for its latest release and, where it has one, its GitHub repository for open issues.

How to choose

• Publishing posts for yourself or your company: the built-in LinkedIn node.
• Lead form responses from LinkedIn ads or pages: a Webhook trigger with the Lead Sync API, as above.
• Profile, company or job data, or other LinkedIn automation: a community node for the service you use.
• Posting the same content to several networks: a multi-network package such as nashir or Repliz.

To install a package on a self-hosted instance, an owner or admin enters its npm name in Settings > Community Nodes; full steps are in How to Install n8n Community Nodes. On n8n Cloud only verified community nodes can be installed, see Verified vs Unverified n8n Community Nodes. Similar guides: WhatsApp, Telegram and Discord.

FAQ

What can the built-in LinkedIn node do?

Create a post, as a person or as an organization, with text and optionally images or an article URL.

How do I post to a LinkedIn company page from n8n?

Set Post As to Organization and enter the organization number. Your LinkedIn app must pass the Community Management App Review first.

Is there a LinkedIn trigger in n8n?

No LinkedIn trigger node, but you can receive lead form responses with a Webhook trigger and LinkedIn’s Lead Sync API.

What is the most used LinkedIn community node?

n8n-nodes-browserflow, with 61,793 weekly npm downloads on 27 October 2026.