Resources · n8n integration

LinkedIn n8n integrationAutomate LinkedIn with n8n.

Publishing should not be the one manual step left at the end of a workflow. The LinkedIn n8n integration exposes a single operation, Create a post, on one resource. No trigger node exists for LinkedIn, so a Schedule or a Webhook starts the run. Useful when the text is written elsewhere and only needs to land.

Try the LinkedIn integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the LinkedIn n8n integration actually cover?

The LinkedIn node is the publishing end of a workflow. It takes text, and optionally an image or an article URL, and posts it to LinkedIn as a person or as a company page. That is the whole surface: 1 resource, 1 operation, no listening side. Everything upstream, where the content comes from and when it goes out, belongs to the other nodes in the workflow.

The most common setup is a content calendar. Rows sit in a spreadsheet with a date and a body, a Schedule Trigger runs each morning, and the row due today goes through post.create. Pair it with the Google Sheets node and the sheet stays the place where people write, while n8n handles the posting rhythm.

Second pattern: repurposing. A new video, a new article, a note already sent to a list, all of them can end as a LinkedIn post with the article URL attached through Media Category set to ARTICLE. Workflows that already touch YouTube or X (Formerly Twitter) get the LinkedIn version for the cost of one extra node.

Third pattern: approval before publication. The draft goes to a person first, by mail through Gmail or into a channel through Slack, and the LinkedIn node sits behind an IF node that only runs once someone has said yes. Handy when the account belongs to a founder who wants to read the text before it goes out.

Prefer the HTTP Request node when the job is not publishing. The node creates posts and nothing else, so reading a feed, fetching analytics or touching any other endpoint means calling the LinkedIn API directly. HTTP Request reuses the same credential through predefined authentication, so there is no second login to manage.

Two limits worth knowing before building. Posting as an organization is not just a field to fill: the developer app has to go through LinkedIn's Community Management App Review, and the credential works with API version 202404. And because there is no LinkedIn trigger, nothing in a workflow can react to activity on LinkedIn itself. If that is a blocker, the n8n review goes through what the platform does and does not do.

Connect

How do you connect LinkedIn to n8n?

  1. 01

    Create the developer app

    Log into LinkedIn and create a new developer app. It asks for an App name, something like n8n integration, a LinkedIn Page to associate the app with, an App logo, and a checkbox for the legal agreement. The company page is a prerequisite, not a detail: an app with no page attached cannot be created, and the form offers a link to make one on the fly if none exists yet.

  2. 02

    Enable the right products

    Creating the app opens the Products tab. For the node to work, request Share on LinkedIn and Sign In with LinkedIn using OpenID Connect. Add Advertising API if the posts go out under an organization account rather than a personal one. Access is granted per product, so the credential will stay broken until those requests come back approved on the LinkedIn side.

  3. 03

    Fill the credential in n8n

    Open the Auth tab of the app, copy the Client ID and the Primary Client Secret, then paste them into the n8n credential. Two methods exist: Community Management OAuth2 for a new account or a newly created app, and OAuth2 for older LinkedIn apps and accounts. A credential is created once in the Credentials menu and picked from the node's dropdown in every workflow after that.

Actions

What the LinkedIn node can do

The LinkedIn node exposes 1 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreate
Post✓

Post

1 operation
01

Create a post

post.create

What you see in n8n

Notes & use cases

Publishes a post on LinkedIn as a profile update or a page update.

Key parameters

  • Post As: person or organization.
  • Person Name or ID: required, from the list or {{ $json.person }}.
  • Organization URN: the page number alone, for example 1234567.
  • Text: the post body, often {{ $json.text }}.
  • Media Category: NONE, ARTICLE or IMAGE, which unlocks Additional Fields: Title, Description, Original URL, a second Input Binary Field for the thumbnail, and Visibility.
  • Input Binary Field: required, the file to post.
Use cases
a scheduled row from a spreadsheet, or an Article post with Original URL and Title for a clean preview.
Need help

Need help automating LinkedIn with n8n?

A person reads every message.

FAQ

LinkedIn and n8n, common questions

01Is the LinkedIn n8n integration free?
Yes on the n8n side. The LinkedIn node ships with n8n, so there is nothing to install and no add-on to buy, and it behaves the same on n8n Cloud, the hosted offer run by n8n, as on a self-hosted instance installed through Docker or npm. A workflow built on one runs on the other without changes. What sits outside that is the LinkedIn side: the developer app, the products you request, and the review process for posting as an organization. Those follow LinkedIn's own rules, not n8n's, and the node cannot bypass them.
02What credentials do you need for the LinkedIn node?
A LinkedIn account, a company page, and a developer app that gives you a Client ID and a Client Secret. Two authentication methods are supported: Community Management OAuth2, meant for new LinkedIn users or newly created apps, and OAuth2, meant for older apps and accounts. The app also needs the right products enabled, Share on LinkedIn and Sign In with LinkedIn using OpenID Connect, plus the Advertising API when the account is an organization rather than an individual. The credential is created once in n8n and reused across every workflow that talks to LinkedIn.
03What are the limits of the LinkedIn node in n8n?
The node does one thing: create a post. One resource, one operation, nothing to read back. It cannot fetch a feed, pull comments, or return metrics, so anything beyond publishing goes through the HTTP Request node, which calls any endpoint of the LinkedIn API while reusing the same credential through predefined authentication. The other real limit is organizational: posting under a company page requires putting the developer app through LinkedIn's Community Management App Review, and the credential works with API version 202404. Plan that approval before promising a client an automated company feed.
04Does the LinkedIn node react in real time?
No, because there is no LinkedIn trigger node in n8n. Nothing in a workflow can wait for something to happen on LinkedIn. A workflow that publishes there starts with another entry point: a Schedule Trigger that fires at a fixed interval, which fits a posting calendar well, or a Webhook, an n8n URL that an outside service calls when it has something to say. The trigger of another tool works too, so a new row in a spreadsheet or a message in a channel can be what sets the post in motion.
05n8n or Make for LinkedIn?
It depends on where you want the workflow to live and how you want to pay for it. Make is hosted by Make, with no self-hosting option, and billed per operation, so the cost follows volume. n8n runs on its own Cloud or on your own server, which matters when the data going through the workflow has to stay in house. On LinkedIn specifically, both sides publish posts, so the choice rests on hosting, data control and the cost model rather than on the node itself. Neither one invents a LinkedIn trigger that does not exist.
Same platform

Other docs you might need on this stack.

Browse all integrations