Not connectable yet
You cannot connect LinkedIn to FounderReply today: the app is still in LinkedIn’s review, the dashboard disables the button, and the authorisation endpoint refuses the request. When it opens it will publish to your own profile only. LinkedIn has no public API for commenting on other people’s posts, and none for member messaging.
You cannot connect LinkedIn to FounderReply today. LinkedIn write access depends on approval of the w_member_social scope, and reading comments even on your own posts needs a permission LinkedIn grants to selected developers only. Until both land, connecting would produce a token that cannot do anything useful. The connect button is disabled in the dashboard and the authorisation endpoint refuses the request, so nothing on this page is available to switch on yet — on any plan.
On LinkedIn
Publishing to your own profile. No comments on others, no DMs — LinkedIn has no API for either.
The one thing LinkedIn’s API genuinely supports for a member account: posting your own content, with images.
Writes go through the Posts API and depend on approval of the w_member_social scope; without it the token exchange succeeds and every write returns 403.
The agent can post a comment reply, but discovering the comment to reply to is currently blocked by LinkedIn.
Reading comments on a member’s own posts needs a restricted permission granted to select developers; the default scope can write a comment but cannot read one.
This is a platform limit, not a roadmap item. LinkedIn publishes no API for either, so the capability is switched off rather than faked.
Commenting on posts you do not own and member-to-member messaging are both marked unsupported in the connector and rejected before a request is ever made.
The room
LinkedIn is the one network where a professional identity, a company and a buying role sit on the same profile, which is why B2B founders keep returning to it. The distribution that works there is your own posting, consistently, from an account people recognise — the part LinkedIn’s API actually supports.
LinkedIn’s Professional Community Policies forbid software that automates activity — automated commenting and automated outreach in particular. That is why the only capability the connector will ever run unattended is publishing your own content, and why the scraper-style tools in this category live outside the rules.
The ceiling
Two layers decide whether an action happens by itself: your autonomy dial, and a hard ceiling we impose per platform. The safer of the two always wins, so the dial can make things stricter and never looser. This table is generated from that ceiling.
| Action | Ships as | Most permissive allowed |
|---|---|---|
| Publish your own postOriginal content from your connected account | Waits for your approval | May run automatically |
| Reply on your own postsAnswering comments left on your content | Waits for your approval | Waits for your approval |
| Direct messagePrivate messages to a person | No API on LinkedIn | No API on LinkedIn |
| Comment on someone else’s postThe highest-risk action on every platform | No API on LinkedIn | No API on LinkedIn |
LinkedIn’s Professional Community Policies forbid software that automates activity. Publishing your own posts may run unattended; replies are held for a human; commenting on other people’s posts is off entirely — and unsupported by LinkedIn’s API regardless. These ceilings are already in the controller and apply the moment the platform opens.
The member flow requests three scopes. Company-page posting needs organisation scopes and LinkedIn marketing-partner approval, which are not requested.
Nothing here is a marketing paraphrase — it is the string the connect flow sends, copied from lib/connectors/linkedin.ts.
openid profile w_member_socialFAQ
No. LinkedIn is marked coming-soon in the platform registry, the dashboard renders it without a connect button, and the authorisation endpoint returns an error before it looks at anything else. Nothing on this page is available to buy or switch on yet.
No, and not later either. LinkedIn publishes no API for commenting on posts you do not own, so the capability is switched off in the connector rather than approximated with a browser script. Tools that do this are automating the website, not the API.
No. There is no official member-messaging API for third-party applications, so direct messages are unsupported and the connector refuses them outright. Automated outreach is also specifically named in LinkedIn’s Professional Community Policies.
We do not publish a date, because the date is not ours. It depends on LinkedIn approving the app and the write scope, and on a restricted read permission we may never be granted. When the status flips, the connect button appears in the dashboard with no other change.
LinkedIn is not connectable yet. Reddit, X, Bluesky, Lemmy and Discourse are — and the approval queue works the same way on all of them.