LinkedIn is a professional network. With the LinkedIn connector, users can publish and manage posts, comments, and reactions as themselves or as a Company Page, and look up organizations.
Authentication Types
LinkedIn supports 1 authentication method:
- OAuth - Create your own LinkedIn app and connect each user with their LinkedIn account.
- Pros: Secure, per-user tracking, actions run as the connected member
- Cons: Requires a LinkedIn Company Page to create the app, and some features need LinkedIn's approval
- Best for: Organizations that want users to post and engage on LinkedIn through AI
Setting up OAuth
To use LinkedIn with Willow, you need to create a LinkedIn app and configure OAuth authentication.
1. Create a LinkedIn app
-
Go to https://www.linkedin.com/developers/apps and sign in
-
Click Create app
-
Fill in the app details:
- App name (e.g., "Willow Integration")
- LinkedIn Page - your company's LinkedIn Page. You must be an admin of this Page.
- App logo
-
Accept the legal agreement and click Create app
-
In the Settings tab, click Verify next to your Company Page and send the generated link to a Page admin to approve
2. Add products
-
Go to the Products tab
-
Click Request access on these two products (both are approved instantly):
- Sign in with LinkedIn using OpenID Connect - grants
openid,profile, andemail - Share on LinkedIn - grants
w_member_social
- Sign in with LinkedIn using OpenID Connect - grants
-
(Optional) To read posts and comments, post as a Company Page, or use the organization tools, request the Community Management API product. LinkedIn reviews these requests, which can take days or weeks.
3. Configure the redirect URL and copy credentials
-
Go to the Auth tab
-
Under OAuth 2.0 settings → Authorized redirect URLs for your app, click the edit icon and add:
- For SaaS deployments:
https://{org}.withwillow.ai/{org}/api/auth/callback - For On-Premise deployments:
{connectUrl}/{org}/api/auth/callback
tipYou can find the exact Redirect URI in Willow when configuring the LinkedIn connector in the Setup tab → Authentication → OAuth section.
- For SaaS deployments:
-
Click Update
-
Under Application credentials, copy the Client ID and the Primary Client Secret
4. Configure in Willow
-
In Willow, go to MCP Servers → + Add MCP Server
-
Find and select LinkedIn and click Use
-
Select the risk level of the tools to share and click Create
-
Under Setup tab, Authentication, select OAuth
-
Paste your Client ID in the Client ID field
-
Paste your Client Secret in the Client Secret field
-
Select the scopes to request. Only select scopes your LinkedIn app has been granted (see the table below).
-
Click Save Changes
5. Test the Connection
-
On the MCP Gateway, go to MCP Servers
-
Find LinkedIn and click Connect
-
In a pop-up window, you'll be redirected to LinkedIn to authorize the app
-
Click Allow
-
You'll be redirected back to Willow with a successful connection
Scopes
| Scope | LinkedIn product | What it enables |
|---|---|---|
openid, profile, email | Sign in with LinkedIn using OpenID Connect | Get the connected member's profile |
w_member_social | Share on LinkedIn | Create, update, and delete posts, comments, and reactions as the member |
r_member_social | Community Management API (approval required) | Read the member's posts and comments |
w_organization_social | Community Management API (approval required) | Post, comment, and react as a Company Page |
r_organization_social | Community Management API (approval required) | Read a Company Page's posts and comments |
r_organization_admin | Community Management API (approval required) | Look up organizations the member administers |
By default, Willow requests openid, profile, email, and w_member_social, which work with any LinkedIn app.
Troubleshooting
"unauthorized_scope_error" during authorization
Cause: Willow is requesting a scope your LinkedIn app hasn't been granted. This usually happens when a Community Management API scope is selected before LinkedIn approved that product.
Solution:
- In your LinkedIn app, go to Auth → OAuth 2.0 scopes to see the scopes your app has
- In Willow, deselect any scope not listed there and click Save Changes
- Try connecting again
Redirect URI mismatch
Cause: The redirect URL in your LinkedIn app doesn't exactly match the one Willow uses.
Solution:
- Copy the exact Redirect URI from Willow
- In your LinkedIn app, go to Auth → Authorized redirect URLs for your app
- Add the URL exactly as shown, including
https://, and click Update
Users need to reconnect every 60 days
Cause: LinkedIn access tokens expire after 60 days, and LinkedIn only issues refresh tokens to approved partner apps.
Solution: This is expected. When the token expires, users click Connect on LinkedIn again to re-authorize.
"Access denied" when posting as a Company Page
Cause: The connected member isn't an admin of the Page, or the app doesn't have w_organization_social.
Solution:
- Confirm the member has an admin role on the Company Page
- Confirm your app has the Community Management API product and that
w_organization_socialis selected in Willow - Disconnect and reconnect so the new scope is granted