Post to LinkedIn with Grok
Grok connects to your inbox, your calendar and your CRM, but not LinkedIn. WoopSocial's connector lets Grok publish and schedule posts to your profile and your company Page, including the scheduling LinkedIn's own API doesn't offer.
Get your free WoopSocial API key
Free API key in under 70 seconds.
Grok Knows Your Work Stack. It Can't Reach LinkedIn.
Grok's connector shelf lists out Gmail, Outlook, Microsoft Teams, SharePoint, Salesforce, Hub Spot and Notion - quite a list for an actual professional's workday. However, LinkedIn is nowhere to be seen on that shelf, which feels a little off given how fully connected everything else in it is.
Adding LinkedIn yourself isn't as easy as it looks, and the gaps are specific to this one platform. One has to go through the Community Management API step, Development then Standard, a screencast video submission for the approval process, and the Development tier has an equally small maximum number of calls per day on top of everything else so it's not something you quietly test your way through without eventually applying for Standard access. Access tokens expire every 60 days, so whatever you build will need its own refresh cycle on top of everything else forever.
The legacy /ugcPosts endpoint is deprecated in favor of /rest/posts, which requires a mandatory LinkedIn-Version header, miss it and requests just quietly fail, with no error pointing you to the root cause. Personal profiles and company Pages also run on different scopes entirely, w_member_social versus w_organization_social, so covering one isn't covering the other - it's two integrations.
And here's what matters the most for an agent use case, especially one built around recurring, scheduled work like Grok's Automations is - LinkedIn's API has no scheduling endpoint at all. POST /rest/posts publishes immediately, there's no scheduled_at parameter and no draft-to-publish flow, so a queue is entirely your own project to build. Our LinkedIn API Alternative guide covers the full picture.
WoopSocial Is Grok's LinkedIn Connector
The scheduling point matters most, so it's worth leading with: LinkedIn's API has no scheduling endpoint, WoopSocial's does. That means Grok can genuinely queue LinkedIn content ahead of time; LinkedIn's API can't m.
Profile and Page as separate targets: Profile and Page independently: one request can post to your Profile and your company Page with different copy sent together (e.g. your personal voice on your feed and a more formal voice on your company Page).
Link preview cards: you can share an article or a landing page and it publishes with a proper preview card attached, not just a bare URL.
WoopSocial is already an approved Community Management API client so there's no screencast, no two-tier app, no waiting around for Standard-tier approval before you can get the posts flowing. Your Grok agent doesn't even store your LinkedIn credentials - it only stores your Woop Social API key. WoopSocial handles token refresh, the version headers, and the media flow in the background so none of that is your problem and the separate personal and company scopes are handled on WoopSocial's end.
Connect Grok to LinkedIn in 3 Steps
Step 1: Get your WoopSocial API key
Free and takes just about 70 seconds. Connect your LinkedIn profile and, if you have one, your company Page inside the WoopSocial dashboard.
Step 2: Add WoopSocial in Grok
Go to grok.com/connectors, click on New Connector, then Custom. Name it WoopSocial, enter the server URL https://api.woopsocial.com/mcp, and complete the authorization prompt Grok shows you.
Step 3: Tell Grok to post
"Turn this Salesforce win into a LinkedIn post for my profile, and a more formal version for the company Page. Schedule both for Tuesday at 8am."
No LinkedIn developer app, no Standard-tier app, no screencast to record, no scheduling queue to build yourself. If you're using Grok Bot instead, here's the slightly different route: Settings, Plugins, add a custom connector, and then the server URL and an authorisation header with your WoopSocial API key instead of the OAuth flow web uses.
LinkedIn, in Plain Language
Once it's connected, this is genuinely how you'll talk to it:
- "Post this to my profile now"
- "Schedule the company Page version for Thursday at 9am"
- "Share this article with a preview card"
- "Draft it and hold it for my review"
Each of those maps to something the connector actually does, LINKEDIN_PAGES and SCHEDULE_FOR_LATER for the queued Page post, the link field for the preview card, DRAFT status for the hold-and-review request, not a wishlist of things that sound good to hear.
Why WoopSocial
The same connector also gives Grok Facebook, Instagram, TikTok, YouTube, Threads, Pinterest and Bluesky - all set up once, and not per platform.
Pricing is flat and predictable: free to start, $19/month for Pro, scaling to $49 for Business and $799 for Max, with API and MCP access included on every tier, free included. WoopSocial tracks LinkedIn's monthly API versions on your behalf, so bumps and updates are its problem to track, not yours.
Grok Already Knows Your Work. Now It Can Post to LinkedIn.
Get your free WoopSocial API key
See how Grok connects to every platform · Post Grok content to Facebook · Post Grok content to YouTube
FAQ
Can Grok post to LinkedIn?
Not directly. Grok's connectors cover Gmail, Outlook, Teams, SharePoint, Salesforce, HubSpot and Notion, but not LinkedIn. Adding WoopSocial as a custom connector is what closes the gap.
Can Grok schedule LinkedIn posts?
Yes, and this is the standout point - LinkedIn's own API has no scheduling endpoint at all, posts publish immediately with no way to queue them. WoopSocial's scheduling bridges that gap.
Can Grok post to a company Page?
Yes, this is possible. WoopSocial treats your personal profile and your company Page as separate targets, so Grok can update your personal profile and your Page with a single request, with each having its own copy if you prefer.
Does Grok need my LinkedIn password?
No. Grok only ever holds your WoopSocial API key. WoopSocial manages your LinkedIn access, including token refresh, on its own side.