Not connectable yet
You cannot connect Facebook to FounderReply today: the Meta app is still in review, the dashboard disables the button and the authorisation endpoint refuses. When it opens it covers Pages only — personal-profile posting has no API. It publishes, replies to comments on your Page, and answers Messenger inside Meta’s 24-hour window.
You cannot connect Facebook to FounderReply today. Most of the permissions this connector needs — managing Page posts, Page engagement and Messenger — require Meta app review before they work for anyone beyond a few test users. Connecting before that completes would produce a Page token that fails on the first write. 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 Facebook
Pages only, via Meta. Page posts, comment replies, Messenger inside 24 hours.
Everything happens on a Facebook Page you manage. Posting to a personal profile is not supported by Meta and is not attempted here.
Authorisation enumerates the Pages your account manages and stores a Page access token; the personal profile never becomes an acting identity.
The agent answers comments left on your Page’s posts. Commenting on other Pages’ content has no official endpoint and is off.
Page engagement is a requested permission; commenting on posts the Page does not own has no Graph API surface, so the capability is marked unsupported.
Free-form Messenger replies work for 24 hours after someone messages you. Outside it, Meta rejects the send and the agent reports it.
The 24-hour rule is enforced by Meta; the connector returns the refusal as a failed action rather than retrying it or reaching for a message tag.
The room
Facebook still carries the local and interest-community half of the internet, and for a lot of small businesses the Page inbox is the actual sales channel. The API reflects that: it is generous about your own Page and silent about everyone else’s, which shapes what any honest tool can do here.
Meta’s platform terms allow automated publishing of your own content and treat automated interaction with other accounts as engagement automation. On a Page, that means the compliant surface is your own posts, your own comment threads, and inbound messages.
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 | May run automatically |
| Direct messagePrivate messages to a person | Waits for your approval | Waits for your approval |
| Comment on someone else’s postThe highest-risk action on every platform | No API on Facebook | No API on Facebook |
Meta’s platform terms permit automated publishing of your own content but treat auto-messaging and auto-commenting on other accounts as engagement automation. Page publishing and replies on your own posts may run unattended; DMs and comments on others are held for a human. These ceilings are already in the controller and apply the moment the platform opens.
You authorise the Pages you manage, and the connector stores a Page access token rather than a personal one. Every scope below needs Meta app review.
Nothing here is a marketing paraphrase — it is the string the connect flow sends, copied from lib/connectors/facebook.ts.
pages_show_list
pages_manage_posts
pages_read_engagement
pages_manage_engagement
pages_messaging
business_managementFAQ
No. Facebook is marked coming-soon in the platform registry, so the dashboard offers no connect button and the authorisation endpoint refuses the request. Nothing on this page is available to switch on yet, on any plan.
No. Meta provides no publishing API for personal profiles, so the connector operates only on Pages you manage and stores a Page access token. If your business runs from a personal profile, creating a Page is a prerequisite rather than a preference.
No. There is no official Graph API endpoint for commenting on content the Page does not own, so the capability is switched off. Meta additionally treats automated commenting on other accounts as engagement automation, which risks restriction by itself.
Meta rejects the message. The connector surfaces that rejection as a failed action rather than retrying or working around it, because sending outside the window without an approved message tag is a policy violation, not a technical obstacle.
Facebook is not connectable yet. Reddit, X, Bluesky, Lemmy and Discourse are — and the approval queue works the same way on all of them.