LinkedIn API + n8n Automation Issue: Not Getting Person URN from /v2/me (Separate Dev App & Posting Account Setup)

Questions
,
1

I am using this follow Automated LinkedIn content creation with GPT-4 and DALL-E for scheduled posts | n8n workflow template .. for the Person account but i need the URN but it not working.

I’m building an automated LinkedIn posting system using n8n and I’m stuck on a critical issue. I need help from anyone who has experience with LinkedIn API + n8n workflows.
My setup:

  • I created a LinkedIn Developer App (separate account from my main LinkedIn profile)

  • My LinkedIn account (where I want to post) is on a different login than the Developer App

  • I am using n8n for automation (AI-generated content + posting workflow)
    Problem:
    Even though:

  • OAuth connection is successful

  • Scopes are correctly set (openid, profile, w_member_social, email)

  • HTTP request to https://api.linkedin.com/v2/me is working
    I still have a major issue:

  1. I am NOT getting the Person URN from the LinkedIn API response

  2. Because of that, the n8n “Create a Post” node does NOT show or load any “Person Name or ID”

  3. Even when I try manually, the post does not publish

  4. The workflow fails at the final posting step
    What I need help understanding:

  • Is it required that the LinkedIn Developer App and LinkedIn personal account MUST be the same account?

  • Why am I not receiving a usable URN from /v2/me?

  • Why does the n8n LinkedIn node not allow posting even when OAuth is connected?

  • Is there a limitation or missing permission that blocks identity retrieval?
    My goal:
    Fully automated LinkedIn posting using n8n with AI-generated content + images, but I’m blocked at the identity/URN step.
    If anyone has solved this setup, I would really appreciate guidance.

Output returned by the last node

Problem in node ‘HTTP Request‘
Unable to sign without access token

  • n8n version: 2.16.1

  • Operating system: Windows

4

I am using these scopes: openid, profile, w_member_social, email, but still nothing appears in the “Person Name or ID” field inside the LinkedIn Create a Post node in n8n (no dropdown or selectable account is shown).

The issue is that the LinkedIn Create a Post node is relying on a fixed internal OAuth2 setup that is outdated or not fully compatible with LinkedIn’s current API permissions. Because of this, it cannot automatically resolve or display the authenticated user identity (URN), even when OAuth is successfully connected.

6

@Ahsan the dev app and the posting account don’t have to be the same, but the OAuth flow must be authorized BY the account you want to post from — if you logged in as the dev app owner during the OAuth consent screen that’s why /v2/me returns the wrong identity. Reconnect your LinkedIn OAuth2 credential in n8n and make sure you sign in as YOUR posting account during the consent popup. Here’s a minimal workflow that grabs the URN and posts:

delete your existing LinkedIn credential in n8n, recreate it, and this time log in with the account you actually want to post from — the id field from /v2/me is your person URN.