Facebook — how to connect

Posts to your Facebook Pages (Meta does not allow posting to a personal timeline). Connect with OAuth after adding your Meta app's App ID and secret below, or paste a long-lived System User page token directly.

Facebook posting works through a Facebook Page, not a personal profile. You can connect either by OAuth (after registering a Meta app) or by pasting a long-lived System User Page token — the adapter needs the same App ID/Secret either way.

Before you start

A Facebook Page you administer (Admin role) — Meta does not allow posting to a personal timeline, only to a Page.
A Meta Developer app with FACEBOOK_APP_ID and FACEBOOK_APP_SECRET configured (developers.facebook.com), OR — as an alternative to OAuth — a Business Manager System User with a generated, non-expiring Page access token.
pages_show_list, pages_read_engagement, and pages_manage_posts granted to the app. For Pages the app's own Business doesn't own, this requires the app to pass App Review plus Meta Business Verification (legal entity + domain checks), which can take days to weeks.
The connecting Facebook user's account should have any 2FA/login checks resolved before authorizing — Meta frequently blocks or silently drops Pages during the OAuth token exchange otherwise.

Step by step

1
Create a Meta app
Go to Meta for Developers → My Apps → Create App, choose the "Business" type, and note the App ID and App Secret shown in Settings → Basic.
Open
2
Add Facebook Login and the Pages permissions
Add the Facebook Login use case to the app and request the pages_show_list, pages_read_engagement, and pages_manage_posts permissions.
Open
3
Enter App ID and App secret in this tool
Paste the App ID and App Secret from Settings → Basic into the connect form's config fields.
4
Connect via OAuth
Click Connect, log in as a Page admin, and approve the Pages permissions — the app pulls in one connected channel per Page you manage.
5
Or paste a System User Page token instead
In Business Manager → Business Settings → System Users, create/select a System User, generate a token for the target Page with pages_manage_posts, and paste that Page ID and Page access token into the credential fields.
Open

App keys (set once in Settings)

App ID (client ID)
developers.facebook.com → your app → Settings → Basic → "App ID". Create a Business-type app first. Posts go to Facebook Pages — Meta does not allow posting to a personal timeline.
App secret (client secret)secret
Same app → Settings → Basic → "App Secret" (click Show). Keep it server-side only; never expose it in a browser.

Paste when you connect

Page ID
Your Facebook Page → About → Page transparency, or Meta Business Suite → Settings → Pages.
Page access token (System User)secret
Business Manager → System Users → generate a token for this Page with pages_manage_posts. Long-lived / non-expiring.

Good to know

You must be an admin of the target Facebook Page (or a System User with Page admin access) — Meta does not allow posting to a personal timeline at all, only to Pages.
pages_manage_posts requires Meta App Review (Advanced Access) before it works for any Page you don't personally administer as a developer/tester on the app — plan for review lead time if this is used beyond your own Pages.
The System User token path (Business Manager → System Users) is long-lived/non-expiring and avoids re-auth, unlike the OAuth-issued Page token which can expire and needs reconnecting.
The app uses Graph API v25.0 (graph.facebook.com/v25.0) — Meta version-sunsets APIs on a rolling schedule, so re-check the app's Graph API version against Meta's current version support table periodically.

Troubleshooting

Connect finishes but no Pages show up to pick from (empty /me/accounts), even though you admin a Page.: Confirm pages_show_list (and often business_management) is Approved/Advanced Access in the app's Meta Developer dashboard, not just requested — Development-mode apps only see Pages owned by admins/testers of that specific app. Also re-check the OAuth consent screen: Facebook lets the user deselect individual Pages during login, so re-authorize and make sure the target Page is checked.
Publish to a Page fails with a permissions/OAuth error (Graph error code 200, "permission denied" or similar) despite the connection looking fine.: pages_manage_posts on Pages the app doesn't own needs completed App Review + Business Verification; without it, posting only works on Pages inside the app's own Business Manager. Also verify publishing uses the PAGE access token returned per connected account (from /me/accounts), not the user token from the initial OAuth exchange — the user token will be rejected on /feed, /photos and /videos.
Posting worked for weeks, then suddenly fails with an expired/invalid token error.: OAuth Page tokens derived from a short user token are only long-lived (~60 days) after exchange, and the app auto-refreshes via fb_exchange_token when FACEBOOK_APP_ID/SECRET are set — if refresh silently fails (app creds missing/rotated), the connection needs full reconnect. To avoid recurring expiry entirely, use the credentials path: a Business Manager System User Page token, which does not expire.
Photo or video posts fail even though text-only posts succeed.: Facebook's /photos and /videos endpoints fetch media by public URL (file_url/url params) rather than accepting uploads — if the media host blocks hotlinking, requires auth, or the URL isn't publicly reachable over HTTPS, the Graph API call will fail. Ensure media URLs are public, direct links before publishing, and note video is capped at one per post while images are capped at 10.

Facebook developer docs

Before you start

A Facebook Page you administer (Admin role) — Meta does not allow posting to a personal timeline, only to a Page.

A Meta Developer app with FACEBOOK_APP_ID and FACEBOOK_APP_SECRET configured (developers.facebook.com), OR — as an alternative to OAuth — a Business Manager System User with a generated, non-expiring Page access token.

pages_show_list, pages_read_engagement, and pages_manage_posts granted to the app. For Pages the app's own Business doesn't own, this requires the app to pass App Review plus Meta Business Verification (legal entity + domain checks), which can take days to weeks.

The connecting Facebook user's account should have any 2FA/login checks resolved before authorizing — Meta frequently blocks or silently drops Pages during the OAuth token exchange otherwise.

Step by step

Create a Meta app

Go to Meta for Developers → My Apps → Create App, choose the "Business" type, and note the App ID and App Secret shown in Settings → Basic.

Open

Add Facebook Login and the Pages permissions

Add the Facebook Login use case to the app and request the pages_show_list, pages_read_engagement, and pages_manage_posts permissions.

Open

Enter App ID and App secret in this tool

Paste the App ID and App Secret from Settings → Basic into the connect form's config fields.

Connect via OAuth

Click Connect, log in as a Page admin, and approve the Pages permissions — the app pulls in one connected channel per Page you manage.

Or paste a System User Page token instead

In Business Manager → Business Settings → System Users, create/select a System User, generate a token for the target Page with pages_manage_posts, and paste that Page ID and Page access token into the credential fields.

Open

App keys (set once in Settings)

App ID (client ID)

developers.facebook.com → your app → Settings → Basic → "App ID". Create a Business-type app first. Posts go to Facebook Pages — Meta does not allow posting to a personal timeline.

App secret (client secret)secret

Same app → Settings → Basic → "App Secret" (click Show). Keep it server-side only; never expose it in a browser.

Good to know

You must be an admin of the target Facebook Page (or a System User with Page admin access) — Meta does not allow posting to a personal timeline at all, only to Pages.

pages_manage_posts requires Meta App Review (Advanced Access) before it works for any Page you don't personally administer as a developer/tester on the app — plan for review lead time if this is used beyond your own Pages.

The System User token path (Business Manager → System Users) is long-lived/non-expiring and avoids re-auth, unlike the OAuth-issued Page token which can expire and needs reconnecting.

The app uses Graph API v25.0 (graph.facebook.com/v25.0) — Meta version-sunsets APIs on a rolling schedule, so re-check the app's Graph API version against Meta's current version support table periodically.

Troubleshooting

Connect finishes but no Pages show up to pick from (empty /me/accounts), even though you admin a Page.

Confirm pages_show_list (and often business_management) is Approved/Advanced Access in the app's Meta Developer dashboard, not just requested — Development-mode apps only see Pages owned by admins/testers of that specific app. Also re-check the OAuth consent screen: Facebook lets the user deselect individual Pages during login, so re-authorize and make sure the target Page is checked.

Publish to a Page fails with a permissions/OAuth error (Graph error code 200, "permission denied" or similar) despite the connection looking fine.

pages_manage_posts on Pages the app doesn't own needs completed App Review + Business Verification; without it, posting only works on Pages inside the app's own Business Manager. Also verify publishing uses the PAGE access token returned per connected account (from /me/accounts), not the user token from the initial OAuth exchange — the user token will be rejected on /feed, /photos and /videos.

Posting worked for weeks, then suddenly fails with an expired/invalid token error.

OAuth Page tokens derived from a short user token are only long-lived (~60 days) after exchange, and the app auto-refreshes via fb_exchange_token when FACEBOOK_APP_ID/SECRET are set — if refresh silently fails (app creds missing/rotated), the connection needs full reconnect. To avoid recurring expiry entirely, use the credentials path: a Business Manager System User Page token, which does not expire.

Photo or video posts fail even though text-only posts succeed.

Facebook's /photos and /videos endpoints fetch media by public URL (file_url/url params) rather than accepting uploads — if the media host blocks hotlinking, requires auth, or the URL isn't publicly reachable over HTTPS, the Graph API call will fail. Ensure media URLs are public, direct links before publishing, and note video is capped at one per post while images are capped at 10.