Your inquiry could not be saved. Please try again.
Thank you! We have received your inquiry.
Connecting LinkedIn to n8n lets you automate tasks like posting updates, fetching profile info, or tracking engagement without the usual manual grind. If you work in a team handling operations or tech workflows, adding LinkedIn into your automation lineup cuts down repetitive work and keeps your data in check. This guide walks you through everything — from grabbing API access, setting OAuth, to testing and building your first workflows.
Before jumping in, it’s good to know what you’re signing up for. This integration lets you automate several LinkedIn tasks, triggered by different events or scheduled actions.
With the LinkedIn node in n8n you can:
It’s all powered by LinkedIn’s API, connecting through OAuth and API calls. You decide what kicks off the workflow and what LinkedIn does when it runs.
Bear in mind, LinkedIn limits some features to certain developer accounts or paid tiers. Basic stuff like posting and reading your info is mostly open, but deep analytics or detailed company data might require extra permissions.
To get LinkedIn talking with n8n, the first step is setting up API access via LinkedIn’s Developer Platform. Here’s what you have to do:
Create a LinkedIn Developer App.
Head over to LinkedIn’s Developer Portal and make a new app. This app represents your connection between LinkedIn and n8n.
Set up OAuth 2.0 Credentials.
LinkedIn uses OAuth 2.0 to handle authentication. You’ll get a Client ID and Client Secret from the app, which n8n uses to connect.
Configure Redirect URLs.
Add n8n’s OAuth redirect URL in your LinkedIn app settings. Usually, this will look like
https://YOUR_N8N_INSTANCE_URL/rest/oauth2-credential/callback
Request API Permissions (Scopes).
Pick and choose scopes based on what you want to do:
r_liteprofile for basic profile info.r_emailaddress to grab the user’s email.w_member_social if you plan to post on a user’s behalf.rw_organization_admin for company page management.Keep it realistic — some scopes need LinkedIn to manually approve your app.
Set App Status to Live (Production).
Your app must be live to access the API for everyone else, not just test users. Don’t skip this if you want proper data from your workflows.
The LinkedIn Developer Portal and n8n docs go into the nitty-gritty, but these are your main building blocks to get started.
OAuth setup gives n8n safe access to your LinkedIn without ever seeing your password. Here’s how you get it working:
In n8n, open Credentials and create a new credential called LinkedIn OAuth2 API.
Paste the Client ID and Client Secret you grabbed from LinkedIn.
Specify which OAuth scopes you want (for example, r_liteprofile r_emailaddress w_member_social).
Enter the Auth URI as:
https://www.linkedin.com/oauth/v2/authorization
For the Access Token URI, use:
https://www.linkedin.com/oauth/v2/accessToken
Make sure the OAuth redirect URI in LinkedIn matches exactly the URL that n8n expects as the Callback URL.
Save and hit Connect. This sends you to LinkedIn’s login page to grant permissions.
Once approved, n8n gets the OAuth token and saves it. Now your workflows can talk to LinkedIn.
Getting these details right is critical — wrong URLs or scopes trip you up fast. The OAuth method lets you keep your data safe since you can revoke n8n’s access anytime without changing your password.
After OAuth’s set, it’s time to add the LinkedIn node to your workflow:
Make a new workflow and drag in the LinkedIn node.
Pick the OAuth credential you created under Authentication.
Select the Resource you want to work with — usually “Posts”, “Profiles”, or “Organizations.”
Pick the Operation from a bunch of options:
For example:
Fill in the key details like the post text, company ID, or filters you need.
Use expressions to make fields dynamic based on earlier steps in your workflow, if you want.
The LinkedIn node handles a lot but watch for API limits and make sure it fits your workflow needs.
Once you have your credential ready, test if it all plays nicely:
Run the LinkedIn node with something simple like “Get Profile.”
Look for your LinkedIn data coming back without errors.
If you hit auth errors, double-check your Client ID, Secret, and Redirect URI — they have to be exact.
Ensure your LinkedIn app is live, not just a developer test app, especially if you’re not the admin.
Verify the OAuth scopes were authorized fully during sign-in.
Testing this early avoids headaches later. After you get a clean response, building workflows that depend on LinkedIn becomes way smoother.
Here’s what you can automate once your LinkedIn and n8n setup is solid:
Post content: Share updates, links, or images to your personal feed or company pages.
Retrieve profile info: Get user details like name, photo, headline, or email.
Manage company data: Grab company details or post updates under a company page’s name.
Engage with connections: Send connection requests or messages, depending on API access.
Query social streams: Search through posts or comments, although this is somewhat limited.
Some things like recruitment features, advanced analytics, or mass messaging need special LinkedIn access or partnerships you probably won’t have out-of-the-box.
LinkedIn doesn’t offer much in the way of real-time event hooks or webhooks. Their API limits these for most devs.
That said, in n8n you can:
Poll LinkedIn regularly for new posts or updates.
Use scheduled checks to trigger workflows on profile or company changes.
Combine LinkedIn data with other sources to spot changes in connections or emails.
Real-time triggers are scarce, but you can mimic them with polling and clever workflows. Keep an eye on LinkedIn’s API updates — they might open more options later.
Here’s a quick rundown on typical connection headaches and how to sort them:
“Invalid Redirect URI” error:
The OAuth redirect URL in your LinkedIn app must match exactly the one used by n8n — including the https part.
Permission or scope denied:
Make sure you authorized the right scopes during login. If you add scopes in your app after the first setup, you’ll need to reauthorize.
App stuck in development mode:
Switch the app to live mode, and submit it for review if needed. Only then will it work for other users.
Rate limit exceeded:
If LinkedIn complains about too many API calls, slow down. Cache results when possible, and avoid polling too often.
OAuth token expired:
Disconnect and reconnect the LinkedIn credential in n8n so it refreshes your tokens.
Start troubleshooting by reading error messages carefully and checking logs in both n8n and LinkedIn’s developer console. Most gotchas come from mismatched credentials or missing permissions.
Once you’re up and running, try these straightforward automations to get the hang of it:
Schedule weekly posts: Automatically share updates on a regular basis.
Send welcome notes: Greet new connections with a personalized message.
Sync profiles to your CRM: Pull in LinkedIn profile data and keep your customer records fresh.
Monitor company page posts: Check for new posts on company pages and trigger alerts.
Collect engagement: Aggregate comments or reactions for marketing insights.
Start small, figure out what LinkedIn’s integration can and can’t do, then add complexity once you’re comfortable.
Connecting LinkedIn to n8n helps you save time on marketing and operational tasks by automating what usually takes plenty of manual effort. This guide showed how to get OAuth set up, grab API access, configure the LinkedIn node, and handle common errors so you don’t get stuck.
Testing early and often makes sure you avoid problems down the road. Use the available actions and polling triggers to build workflows that actually fit your needs.
Keep an eye on LinkedIn’s API changes — they change stuff sometimes and that impacts what you can do.
Go ahead, link your LinkedIn account to n8n today and start building workflows that make your life easier.
You need to create a LinkedIn app, configure OAuth 2.0 settings with proper Redirect URLs, generate Client ID and Secret, then input these in n8n’s LinkedIn credentials.
Basic profile access requires 'r_liteprofile' and 'r_emailaddress'. To post on behalf of a user, include 'w_member_social'. Access to company data needs 'rw_organization_admin'.
Yes, with the right API scopes you can manage both personal and company pages. Personal profiles require basic scopes, while company pages need additional permissions like 'rw_organization_admin'.
LinkedIn enforces limits based on quota categories per app and user. Generally, free tiers have lower limits. Exceeding limits leads to temporary blocks; managing call frequency helps avoid this.
Check OAuth credentials for accuracy, confirm Redirect URIs match, verify required scopes are authorized, and ensure LinkedIn app is in production. Inspect error messages for clues.
