Post to LinkedIn with Muse

Muse Doesn't Connect to LinkedIn

Muse's launch connectors cover Gmail, Google Calendar, Spotify, OpenTable, Plaid, and Meta's own platforms, Facebook, Instagram and Threads, through Accounts Center. LinkedIn is missing - notably, since it's where most professional audiences actually are. Muse will write you a sharp LinkedIn post. It just can't publish it.

Adding LinkedIn yourself is harder than it looks, and the functional gaps are all specific to this one platform. The Community Management API needs both Development and Standard access, with a screencast video component to the review, and Development only extends to a limited call volume, so you can't sneak through using it to experiment without eventually adding Standard access.

Access tokens only last 60 days, so whatever you build has to have its own refresh cycle layered onto 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 fail silently, no error message pointing you at the actual problem, just a request that quietly doesn't do what you expected.

Personal-profile and company-page publishing also operate with separate scopes, w_member_social versus w_organization_social, so posting to both isn't one integration, it's effectively two. The one that hits closest to home in the agent use case is that LinkedIn's API has no scheduling endpoint at all. POST /rest/posts publishes right away, there isn't even a scheduled_at parameter and no draft-to-publish flow, so a queue is completely your own to build. Our LinkedIn API Alternative guide explains more.

WoopSocial Gives Muse LinkedIn Publishing, and Scheduling

One connection, and Muse publishes to LinkedIn, personal profile and company Page as separate targets - plus TikTok, YouTube, X and Pinterest, all through the same connector.

The scheduling point matters most, so it's worth leading with: LinkedIn's API has no scheduling endpoint, WoopSocial's does. That means Muse can genuinely queue LinkedIn content - a capability the native API simply doesn't expose.

The approval point: WoopSocial is already an approved LinkedIn client, so you skip the Community Management API review entirely, no screencast, no two-tier application, no waiting on Standard-tier access before you can post.

The dual-target point: post to your personal profile and your company Page in the same request, with different copy for each.

Your Muse agent never holds LinkedIn credentials. It only ever holds your WoopSocial API key. WoopSocial handles token refresh, the version headers, and the media upload flow behind the scenes.

Connect Muse to LinkedIn in 3 Steps

Step 1: Get your WoopSocial API key

Free, about 70 seconds. Connect your LinkedIn profile and, if you have one, your company Page inside the WoopSocial dashboard.

Step 2: Give Muse the link

One message: "Build a custom integration for WoopSocial using this MCP server: https://api.woopsocial.com/mcp?api_key=YOUR_WOOPSOCIAL_API_KEY. Use bearer token auth with this API key. Test it and save it as a skill." Muse handles the transport and auth questions itself, for a hosted MCP server the answers are usually HTTP and bearer token.

Step 3: Tell Muse to post

"Post this to my LinkedIn profile now, and schedule the company Page version for Tuesday at 8am."

No LinkedIn developer app, no Standard-tier application, no screencast to record, no scheduling queue to build yourself, no code. Something worth repeating - the scheduling is doing something LinkedIn's own API can't do at all, not something WoopSocial merely does more conveniently. And because Muse asks before publishing anything, you'll see a confirmation before a post actually goes live on your profile or your Page, nothing gets out without you seeing it first, scheduled or not.

LinkedIn Posts, in Plain Language

Once it's connected, this is how you'll talk to it:

• "Post this to my LinkedIn profile now"
• "Schedule this for my company Page on Thursday at 8am"
• "Post this to both my profile and the company Page, but make the Page version more formal"
• "Share this article link on LinkedIn with a preview card"
• "Draft this and hold it for my review"

Each of those maps to something the connector is actually handling, contentOverride for the reworded Page, the link field for the preview card, DRAFT status for the hold-and-review request - not a list of random things that just sound plausible. If a request doesn't map to a real field, Muse makes it clear instead of pretending it went through.

One Connector, Every Platform Muse Is Missing

The same connector also gives Muse TikTok, YouTube, X, BlueSky and Pinterest, set up once, 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 maintains the integration and tracks LinkedIn's versioned API changes on your behalf, so when LinkedIn deprecates an endpoint or bumps a version header requirement, that's WoopSocial's problem to track, not yours.

Give Your Muse Agent LinkedIn Publishing

You already have Muse. Closing the gap to LinkedIn is just one message and a free API key, and it gets you scheduling that LinkedIn's own API doesn't provide.

Get your free WoopSocial API key

See every platform Muse is missing