n8n LinkedIn: Fix "Version Not Active" Error + Workflow Template

Figure 1: Connecting n8n to LinkedIn involves more moving parts than most integrations — here's every one of them.

💡 If your n8n LinkedIn workflow suddenly stopped working with "Requested version ... is not active," you're not alone — and it's not something you broke. As of this writing, this is a confirmed bug in n8n's built-in LinkedIn node, tracked in multiple GitHub issues, and it will very likely come back again in about a year even after it's patched. This guide explains exactly why, and gives you a workflow that's immune to it.

🔥 I dug through the actual n8n GitHub issues and community threads to get this right — not just the OAuth setup steps everyone covers, but the LinkedIn-specific "Products" approval system that trips up almost everyone coming from Google or Slack integrations, the exact root cause of the version error (with the pull request that fixes it), and a downloadable HTTP Request-based workflow that won't silently break the next time LinkedIn retires an API version.

1. Setup & OAuth — Why LinkedIn Is Harder Than Google

If you've connected Google Sheets or Slack to n8n before, LinkedIn will surprise you. Google enables an API with one click. LinkedIn makes you request access to named "Products," each of which unlocks a different bundle of scopes — and picking the wrong combination is the single biggest reason people get stuck before they ever touch a workflow.

1.1 Prerequisites

• n8n instance — Cloud or self-hosted, with a publicly reachable HTTPS URL (required for the OAuth redirect).
• A LinkedIn account that will own the app — for company page posting, this account must be an admin of that page.
• A LinkedIn Company Page only if you intend to post as an organization, not just as yourself.

1.2 Create a LinkedIn Developer App

Figure 2: Request only the Products you actually need — over-requesting is the top cause of scope confusion.

2. Node Operations — What the LinkedIn Node Can Do

The built-in LinkedIn node in n8n is intentionally narrow — it covers the core posting action, not the full LinkedIn API surface.

Create Post

• Post as: Person or Organization.
• Person Name or ID / Organization URN: per n8n's own documentation, for an organization you enter just the numeric ID (e.g. 03262013), not the full urn:li:company:03262013 — the node builds the URN for you.
• Text: the post content.
• Media Category: use this for images or shared article links.

One practical tip before you build anything real on top of this: test with a throwaway post first. LinkedIn posts created via the API are visible to your full network immediately, and there's no "draft" state in the standard posting flow — unlike Google Sheets, where a bad write is just a cell you can fix. Confirm your workflow's output looks right using a private test account or a low-visibility audience setting before wiring it into anything that runs unattended.

3. The "Version Not Active" Bug, Explained Properly

This is the error that brought most readers to this guide, so let's be precise about it instead of just telling you to "update n8n."

What's actually happening

LinkedIn's REST API requires every request to include a LinkedIn-Version header, formatted as a year and month (for example 202604). LinkedIn keeps each monthly version active for roughly 12 months, then retires it. When that happens, requests using the retired version fail with:

{
  "status": 426,
  "code": "NONEXISTENT_VERSION",
  "message": "Requested version 20250401 is not active"
}

The root cause, confirmed directly in n8n's GitHub repository: the version value is hardcoded in the LinkedIn node's source file (GenericFunctions.ts), not fetched dynamically. When LinkedIn retires that version, every workflow using the native node breaks at once — for everyone, simultaneously, with no change on your end.

How to check if you're affected right now

1. Run your LinkedIn "Create Post" node once, manually.
2. If it fails with NONEXISTENT_VERSION, update n8n to the latest version first — this alone resolves it if you're on an older release.
3. If it still fails after updating, or you'd rather not depend on n8n's release cycle to catch the next retirement, use the HTTP Request-based approach below.

Finding the current valid API version yourself

If you're building the HTTP Request workaround, you need a currently active LinkedIn-Version value. LinkedIn's official API documentation lists which monthly versions are currently supported at any given time — check it directly rather than trusting a hardcoded value from any tutorial (including this one), since the correct value changes every month by definition. A quick way to sanity-check your chosen version: if a request fails specifically with NONEXISTENT_VERSION rather than a permissions or authentication error, the version header — not your credentials — is what needs updating.

4. 8 Common LinkedIn Errors & How to Fix Them

5. AI-Powered Posting — From Content Pipeline to LinkedIn

Once the connection is solid, LinkedIn becomes a natural final step in a content pipeline: draft with AI, review, publish. This connects directly to the pattern used in the AI Content Factory guide — the same generation step, with LinkedIn as the distribution target instead of (or alongside) a blog post.

Example: Blog Post → LinkedIn Summary

1. Trigger — a new row in a content-tracking Google Sheet (see the Google Sheets Trigger covered in that guide), or an RSS-style check of your own blog feed.
2. AI node — summarize the full article into a LinkedIn-appropriate post: a hook, 2-3 key points, and a link.
3. Code node — enforce a safe character limit on the generated text before it ever reaches the API (see Error 7).
4. HTTP Request → LinkedIn Posts API — publish, using the version-controlled approach from section 8.

A Note on URN Formats

LinkedIn's API identifies entities using URNs (Uniform Resource Names) rather than plain IDs — urn:li:person:{id} for an individual, urn:li:organization:{id} for a company page. The /v2/userinfo endpoint's sub field gives you the raw numeric ID; you build the full URN yourself by prefixing it. This sounds trivial, but it's a common source of silent failures: a post request with a malformed URN often doesn't throw an obvious "wrong format" error — it fails with a generic permissions or validation error instead, which sends people down the wrong troubleshooting path entirely.

6. Native LinkedIn Node vs HTTP Request: Which Should You Use?

My honest recommendation: start with the native node while you're testing a workflow's logic — it's faster to wire up. Before putting anything into unattended production, switch to the HTTP Request pattern in section 8. The migration is a single node swap, not a rebuild.

7. Practical Use Cases for Small Businesses

1. Content Repurposing Pipeline

Publish a blog post once, and have n8n automatically draft and post a LinkedIn summary — turning a single piece of content into consistent presence on both channels without manual copy-pasting.

2. Job Posting Distribution

When a new row appears in a hiring spreadsheet (see the Google Sheets guide for the Trigger setup), automatically format and post it to your company page, keeping recruiting content current without someone remembering to do it manually.

3. Weekly Digest for a Company Page

Aggregate the week's key updates (from a Sheet, a project tracker, or an internal log) into a single scheduled post every Friday — a lightweight way to keep a company page active without a dedicated social media manager.

4. Cross-Posting from a Single Content Source

If you already write once and distribute everywhere — the exact pattern from the Google Sheets guide's content tracker — LinkedIn slots in as one more distribution branch alongside email or your blog. The Sheet stays the single source of truth for "what's been published where," and the HTTP Request node handles the LinkedIn leg without needing a separate content calendar tool.

Figure 3: One content source, multiple distribution branches — LinkedIn is just one more HTTP Request away.

Every one of these follows the same shape: generate or gather content → format for LinkedIn → post via the HTTP Request node. Once that pattern is working reliably, the specific content source is easy to swap.

8. Complete Workflow JSON — Version-Proof LinkedIn Poster

This workflow posts to LinkedIn using the HTTP Request node with your LinkedIn OAuth2 credential applied as a Predefined Credential Type — meaning n8n handles the token for you, while you keep full control over the request itself, including the LinkedIn-Version header that caused the bug in section 3.

{
  "name": "Version-Proof LinkedIn Poster (HTTP Request)",
  "nodes": [
    {
      "parameters": {},
      "id": "manual-trigger",
      "name": "When clicking Execute Workflow",
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [240, 300]
    },
    {
      "parameters": {
        "assignments": {
          "assignments": [
            {
              "id": "post-text",
              "name": "postText",
              "type": "string",
              "value": "Write or generate your LinkedIn post text here."
            },
            {
              "id": "api-version",
              "name": "linkedinApiVersion",
              "type": "string",
              "value": "202604"
            }
          ]
        }
      },
      "id": "set-post",
      "name": "Post Content",
      "type": "n8n-nodes-base.set",
      "typeVersion": 3,
      "position": [440, 300]
    },
    {
      "parameters": {
        "authentication": "predefinedCredentialType",
        "nodeCredentialType": "linkedInOAuth2Api",
        "url": "https://api.linkedin.com/v2/userinfo",
        "method": "GET",
        "options": {}
      },
      "id": "get-member-id",
      "name": "Get Member ID",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [640, 300],
      "credentials": { "linkedInOAuth2Api": { "id": "YOUR_LINKEDIN_CREDENTIAL_ID" } }
    },
    {
      "parameters": {
        "authentication": "predefinedCredentialType",
        "nodeCredentialType": "linkedInOAuth2Api",
        "url": "https://api.linkedin.com/rest/posts",
        "method": "POST",
        "sendHeaders": true,
        "headerParameters": {
          "parameters": [
            { "name": "LinkedIn-Version", "value": "={{ $('Post Content').item.json.linkedinApiVersion }}" },
            { "name": "X-Restli-Protocol-Version", "value": "2.0.0" },
            { "name": "Content-Type", "value": "application/json" }
          ]
        },
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "={{ JSON.stringify({\n  author: \"urn:li:person:\" + $json.sub,\n  commentary: $('Post Content').item.json.postText,\n  visibility: \"PUBLIC\",\n  distribution: {\n    feedDistribution: \"MAIN_FEED\",\n    targetEntities: [],\n    thirdPartyDistributionChannels: []\n  },\n  lifecycleState: \"PUBLISHED\",\n  isReshareDisabledByAuthor: false\n}) }}",
        "options": {}
      },
      "id": "post-to-linkedin",
      "name": "Post to LinkedIn",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [840, 300],
      "credentials": { "linkedInOAuth2Api": { "id": "YOUR_LINKEDIN_CREDENTIAL_ID" } }
    }
  ],
  "connections": {
    "When clicking Execute Workflow": { "main": [[{ "node": "Post Content", "type": "main", "index": 0 }]] },
    "Post Content": { "main": [[{ "node": "Get Member ID", "type": "main", "index": 0 }]] },
    "Get Member ID": { "main": [[{ "node": "Post to LinkedIn", "type": "main", "index": 0 }]] }
  },
  "active": false,
  "settings": {
    "executionOrder": "v1",
    "saveManualExecutions": true,
    "executionTimeout": 120
  }
}

9. Frequently Asked Questions

Continue Your n8n Journey