Connect Facebook Messenger
Messenger is a beta reply channel. A customer messages the Page; your hosted or external agent answers inside Meta’s messaging window.
Before you connect
Section titled “Before you connect”You need:
- a Facebook Business Page
- messaging enabled in the Page settings
- admin access to the Page
- owner or admin access in Wabery
A Facebook profile is not the channel. Wabery connects the Page the profile manages.
1. Connect the Page
Section titled “1. Connect the Page”Open your project’s Channels page. Find Messenger (Beta) and select Connect.
Sign in through the Facebook popup, grant the requested permissions, and select the Page customers will message.
2. Test a real message
Section titled “2. Test a real message”Message the Page from a different Facebook account. The thread should appear in Inbox.
What answers it depends on the project:
- Wabery hosted agent — the hosted agent handles the message.
- External agent — your webhook receives
message.received, then your system replies throughPOST /v1/messages.
Messenger is a reply channel in Wabery. Reply on the existing
conversation_id; do not treat a Page-scoped user ID as a phone number.
What works today
Section titled “What works today”| Capability | Messenger beta |
|---|---|
| Inbound messages and Inbox | Yes |
| Text replies | Yes, inside Meta’s window |
| Images, documents, audio, and video | Yes, from a public HTTPS URL |
| Quick replies | Limited support |
| Full Messenger template surface | Not exposed yet |
| Page-comment private replies | Not exposed yet |
| WhatsApp Flows and templates | No |
| Proactive template-style outreach | No |
See Media messages for limits and payloads.
If the connection fails
Section titled “If the connection fails”Check that messaging is enabled, you are a Page admin, and you selected the right Page in the Meta popup. Then check the connection on your project’s Channels page.
After a disconnect, start a new Meta sign-in. Wabery deletes the old access token instead of keeping a dead connection around.