Pipedream LinkedIn steps in n8n

On Pipedream, LinkedIn is mostly used to publish: a new blog post, an RSS item or an LLM draft becomes a LinkedIn post for a person or a company page. n8n's native LinkedIn node covers exactly that and not much more. Everything else goes through the HTTP Request node with the same credential.

The n8n LinkedIn node

n8n-nodes-base.linkedIn has one resource and one operation: Post → Create, posting as a Person or an Organization. For an organization, enter the numeric ID only, without urn:li:company:. There is no LinkedIn trigger node.

Pipedream's LinkedIn app has 22 actions. The gap is real, and it is better to know it before the move.

What maps where

Pipedream (app linkedin)	In n8n	Status
Create a Simple Post (User)	LinkedIn → Post → Create, Post As: Person	manual, 1 node
Create a Simple Post (Organization)	LinkedIn → Post → Create, Post As: Organization	manual, needs org permission
Create Image Post (User / Organization)	LinkedIn → Post → Create with a binary image, check against your app's products	manual
Create Comment, Create Like On Share	HTTP Request to the LinkedIn REST API, LinkedIn credential	manual
Retrieve organization or member data	HTTP Request	manual
New Organization Post Created (source)	Schedule Trigger + HTTP Request listing posts, dedupe by ID	manual

LinkedIn steps are not in the converter's automatic list, so they arrive as placeholder Code nodes with the original props (text, visibility, organization ID) in a comment.

Credentials and LinkedIn app setup

n8n offers two LinkedIn credentials:

• Community Management OAuth2 – the method n8n recommends for new users and new apps.
• OAuth2 – the legacy method; it can also post as an organization through its Organization Support option.

Steps:

1. Create an app in the LinkedIn Developer Portal. It must be linked to a LinkedIn Company Page.
2. Request the products Share on LinkedIn and Sign In with LinkedIn using OpenID Connect. For company posts with the Community Management credential, n8n says to add the Advertising API product; the w_organization_social permission needs LinkedIn's app review.
3. Add the n8n OAuth redirect URL, copy Client ID and Secret into the n8n credential, connect.

Pipedream's connection used Pipedream's own LinkedIn app. Your new app starts without approvals, so request them early; review can take longer than the conversion itself.

Typical migration: blog to LinkedIn

Pipedream: RSS New Item → OpenAI Chat (write a teaser) → Create a Simple Post (Organization). n8n: RSS Feed Trigger (mapped automatically) → OpenAI (Chat converted automatically) → LinkedIn → Post → Create as Organization.

Pitfalls

• Rate limits are daily, per application and per member, reset at midnight UTC, and are not published; check them in the Developer Portal under your app's Analytics. Over the limit returns 429.
• API versions. LinkedIn versions its REST API by month and retires old versions. If you call it with HTTP Request, set the LinkedIn-Version header explicitly.
• Lead Sync webhooks are a separate approval and need an HMAC challenge response within 3 seconds; not something to set up on day one.
• URNs. Many endpoints need full URNs (urn:li:person:…); the node needs the bare org ID. Keep the two apart.

How to move your LinkedIn workflows

1. Export from Pipedream.
2. Upload on /convert; the free report lists LinkedIn steps as manual with their props.
3. Download the n8n JSON (1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon) and rebuild the post node.

Read the Pipedream to n8n guide and check code steps in the code step checker. Related: WordPress, OpenAI, Google Sheets.