Messenger
Connect a Facebook Page through Meta Messenger Platform credentials and signed webhooks.
Connect a Facebook Page through Meta Messenger Platform credentials and signed webhooks.
Prepare the Meta app and Page#
Follow Meta's official Messenger Platform getting-started guide. Add Messenger to a Meta app, connect the Facebook Page that should receive messages, and ensure your account can administer both assets.
Collect values from the same app and Page:
| Make Agent Fast field | Provider value | Purpose |
|---|---|---|
| Page access token | Token issued for the selected Page | Reads Page identity and sends replies |
| App secret | 32-character hexadecimal Meta app secret | Verifies signed inbound webhook requests |
Do not use a user access token or a token belonging to a different Page. Meta app development/review state controls which people can use the integration.
Save and validate credentials#
Open the site's Connectors page, select Messenger, enter the Page access token and app secret, and select Connect.
Make Agent Fast calls the Graph API with appsecret_proof, resolves the Page ID/name, and binds inbound events to that exact Page. The connector card then displays its Webhook URL and Verify token.
Configure the Page webhook#
In the same Meta app:
- Open the Messenger webhook settings.
- Paste the connector Webhook URL and Verify token.
- Complete the verification challenge.
- Select the message event subscription required by the Messenger workflow.
- Subscribe the intended Facebook Page to the app.
- Confirm the Page subscription and app mode permit your test user.
The verify token is used only for the initial challenge. Runtime events must carry a signature that matches the app secret. Make Agent Fast also rejects events addressed to a different Page even if they came from the same Meta app.
Test capabilities#
Send a normal message to the Page from a permitted, non-admin test account and confirm the response plus Conversations thread. Then test an audio attachment if inbound voice matters to your workflow.
Text and supported inbound audio are processed. Replies are text-only in the current Messenger connector, even when the source message was voice. Delivery/read receipts, echoes of the Page's own messages, images, and other unsupported attachments are ignored.
Production readiness#
Complete the permissions, app review, business verification, privacy URL, and Page-publication steps Meta requires for your audience. Development-mode success with an app-role account does not establish that the public can message the Page integration.
Document the owning Meta app and Page ID for operators. A Page token can stop working when its owner, permissions, business association, or provider policy changes.
Rotate or disconnect#
Generate the replacement Page token, update the connector, test from a permitted user, then invalidate the old token. Update Make Agent Fast immediately after rotating the app secret.
Disabling or removing the connector does not unsubscribe the Page in Meta. Remove the Page subscription and unused provider credential when permanently decommissioning the integration.
Troubleshooting#
| Symptom | Fix |
|---|---|
| Token rejected | Confirm it is a Page token for the intended Page and the app secret belongs to the same app |
| Webhook verification fails | Copy the current URL and verify token exactly; use public HTTPS |
| Verification works but messages do not arrive | Subscribe the Page and message event, then check app mode, user role, and Meta delivery logs |
| Requests are unauthorized | Correct the app secret; signed POST requests do not use the verify token |
| Inbound message appears but no reply | Check Page token validity, messaging permissions, provider send error, and connector status |
| Voice gets a text answer | Expected; outbound Messenger voice is not currently supported |
Provider credentials belong only in the authenticated connector form or a trusted server-side API call.