n8n LinkedIn Post Automation: How to Post to LinkedIn from n8n

Path A: the built-in n8n LinkedIn node

The node has one operation, Post > Create, and posts as a Person or an Organization. It is free, but you bring your own LinkedIn developer app. These steps follow n8n's LinkedIn credential and node documentation.

1. 1

   Create a LinkedIn developer app

   Go to the LinkedIn Developer portal and create an app. LinkedIn asks for an app name, a logo, and a LinkedIn Company Page to associate with the app, even if you only want to post as yourself. If you have no Page, the form has a link to create one.

2. 2

   Add both products

   On the app's Products tab, add Share on LinkedIn and Sign In with LinkedIn using OpenID Connect. Share on LinkedIn grants the posting permission. OpenID Connect is what lets n8n look up your member ID for the Person dropdown.

3. 3

   Create the n8n credential

   In n8n, create a LinkedIn OAuth2 credential. Copy the Client ID and the Primary Client Secret from the app's Auth tab, add n8n's OAuth Redirect URL to the app's Authorized redirect URLs, and leave Organization Support and Legacy off. Then click Connect and sign in.

4. 4

   Configure the LinkedIn node

   Add a LinkedIn node, choose Post > Create, set Post As to Person, and pick yourself in Person Name or ID. Write the post in Text.

5. 5

   Add an image or an article (optional)

   Media Category lets you attach an image from an earlier node's binary data, or an article URL with a title and description. The node has no video or multi-image option.

6. 6

   Add a trigger and activate

   Put a Schedule Trigger, an RSS Feed Trigger, or a Google Sheets trigger in front of the node, run it once to test, then activate the workflow.

Path B: post to LinkedIn with one HTTP Request node

Connect LinkedIn once in OpenTweet with a normal LinkedIn sign-in. Your n8n workflow then holds only an OpenTweet API key and calls POST /api/v1/posts with "platforms": ["linkedin"]. No developer app, no Company Page, no OAuth credential in n8n, and no version header to track.

1. 1

   Connect LinkedIn and create a key

   In OpenTweet, go to Settings > Accounts and connect LinkedIn. Posts go to your personal profile. Then create an API key under Settings > API keys. It starts with ot_.

2. 2

   Import the workflow

   Copy the JSON below and paste it onto the n8n canvas. You get an RSS Feed Trigger wired to an HTTP Request node.

3. 3

   Set the feed and the key

   Put your feed URL in the trigger and replace ot_your_api_key in the Authorization header, or move the key into a Header Auth credential so it is not stored in the workflow.

4. 4

   Test, then activate

   Run it once and read the results array in the HTTP Request output. When it looks right, activate the workflow.

Importable workflow: RSS to LinkedIn

n8n-nodes-base.rssFeedReadTrigger polls the feed every hour and sends each new item to n8n-nodes-base.httpRequest, which publishes it to LinkedIn right away. Swap the trigger for a Schedule Trigger to post on a fixed timetable instead.

{
  "name": "RSS to LinkedIn",
  "nodes": [
    {
      "parameters": {
        "pollTimes": {
          "item": [
            { "mode": "everyHour" }
          ]
        },
        "feedUrl": "https://example.com/feed.xml"
      },
      "id": "3d6a1f0e-8b42-4c7e-9a15-6e2b7c9d0a11",
      "name": "RSS Feed Trigger",
      "type": "n8n-nodes-base.rssFeedReadTrigger",
      "typeVersion": 1,
      "position": [0, 0]
    },
    {
      "parameters": {
        "method": "POST",
        "url": "https://opentweet.io/api/v1/posts",
        "sendHeaders": true,
        "headerParameters": {
          "parameters": [
            { "name": "Authorization", "value": "Bearer ot_your_api_key" }
          ]
        },
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "={{ JSON.stringify({ text: 'New on the blog: ' + $json.title + ' ' + $json.link, platforms: ['linkedin'], publish_now: true }) }}",
        "options": {}
      },
      "id": "7f2c9b4a-1e63-4d8f-b0a7-5c3e2d1f9b22",
      "name": "Post to LinkedIn",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [280, 0]
    }
  ],
  "connections": {
    "RSS Feed Trigger": {
      "main": [
        [
          { "node": "Post to LinkedIn", "type": "main", "index": 0 }
        ]
      ]
    }
  },
  "settings": { "executionOrder": "v1" }
}

Queue it for later instead

Replace publish_now with scheduled_date in ISO 8601. The post waits in your OpenTweet queue and publishes at that time, so the workflow does not have to run then.

{{ JSON.stringify({
  text: $json.title + ' ' + $json.link,
  platforms: ['linkedin'],
  scheduled_date: '2026-10-14T08:30:00Z'
}) }}

An n8n LinkedIn image post

Pass public image URLs in media_urls. OpenTweet downloads them, uploads them to LinkedIn, and publishes them as one post. A video URL is skipped on LinkedIn with a reason.

{{ JSON.stringify({
  text: 'Three charts from this week.',
  platforms: ['linkedin'],
  media_urls: [
    'https://example.com/chart-1.png',
    'https://example.com/chart-2.png',
    'https://example.com/chart-3.png'
  ],
  publish_now: true
}) }}

Cross-post to X and Bluesky in the same call

Add the other networks to platforms. Each one gets its own entry in results, and a post that is too long for one network is skipped there while the others still go out. The full three-network workflow is on n8n to X, Bluesky and LinkedIn.

{{ JSON.stringify({
  text: $json.title + ' ' + $json.link,
  platforms: ['x', 'bluesky', 'linkedin'],
  publish_now: true
}) }}

What comes back

{
  "success": true,
  "count": 1,
  "posts": [
    {
      "id": "65f1a2b3c4d5e6f7a8b9c0d1",
      "status": "posted",
      "platforms": ["linkedin"],
      "posted": true,
      "results": [
        {
          "platform": "linkedin",
          "status": "published",
          "url": "https://www.linkedin.com/feed/update/urn:li:share:7300000000000000000/"
        }
      ]
    }
  ]
}