Setting Up the Facebook Messenger Channel
Facebook Messenger uses the same ecosystem as Instagram (Meta), but operates directly with Facebook Pages, without needing a linked Instagram account.
Prerequisites
- A Facebook Page (not a personal profile)
- Administrator access to the Page
- Hub Chatt2.me account with administrator permission on the Application
Connection process
1. Start authorization
In the Hub Chatt2.me dashboard:
- Go to Channels → Activate/Configure → Messenger
- Click Connect with Facebook
2. Authorize on Facebook
- Log in with the Page administrator
- Authorize the messaging permissions
- Select the Facebook Page to be used as a channel
3. Channel ready
The channel UUID will be available in the details after the connection.
Identifying the recipient (to)
On Messenger, to is the PSID (Page-Scoped User ID) — the user's identifier in the context of your Page. It arrives via webhook when the user sends a message to the Page.
Inbound participant fragment:
{
"sender": {
"id": "26203292189261166"
}
}
The PSID (Messenger) and the IGSID (Instagram) are different identifiers even if the user is the same person on Facebook. They are not interchangeable.
Differences from Instagram
| Aspect | Messenger | |
|---|---|---|
Identifier (to) | Page PSID | IGSID |
| Technical Hub session | 24 hours | 24 hours |
| Stickers | Not supported | Supported |
| Documents | Supported as file attachment | Not supported for outbound sends |
| Mark as seen | Supported | Supported |
Limitations
- Like Instagram, it is not possible to initiate conversations with users who have never interacted with the Page
- Ordinary sends require an eligible conversation under the provider's current messaging policy; a technical Hub session is not permission to send
- The Hub uses a 24-hour technical session for Messenger and Instagram. Do not interpret Instagram comment private replies as a seven-day ordinary-send window
- This public message contract does not offer a general provider policy exception or tag-selection field; out-of-policy sends can be rejected
Media formats and limits
| Type | Formats maintained by the current Hub flow | Outbound limit | Inbound mirror limit |
|---|---|---|---|
| Image | JPEG, PNG, GIF, WebP | 25 MB | Provider maximum not published; Hub safety ceiling 2 GiB |
| Audio | MP3/MPEG, M4A/MP4, OGG, WAV; WebM input is converted to M4A | 25 MB | Provider maximum not published; Hub safety ceiling 2 GiB |
| Video | MP4; MOV/QuickTime, AVI, MKV and WebM input is converted to H.264/AAC MP4 | 25 MB | Provider maximum not published; Hub safety ceiling 2 GiB |
| File | PDF, TXT, DOC/DOCX, PPT/PPTX, XLS/XLSX, ZIP | 25 MB | Provider maximum not published; Hub safety ceiling 2 GiB |
Messenger's Send API models these as image, audio, video, and file attachments. The Hub applies
only the audio and video conversions listed above. Meta does not currently publish a stable exhaustive MIME matrix for this API, so
the provider can still reject a file whose container or codec it cannot process.
The inbound 2 GiB value is an operational download protection, not a Meta limit.
Messenger has no native stickerUrl operation. Use imageUrl for the same visual;
stickerUrl returns CHANNEL_MEDIA_NOT_SUPPORTED before provider submission.
Identifying the sender (from)
In POST /v1/communication/messenger/message, set from to the application channel UUID or the Facebook Page username, Page ID, or configured account ID for that channel. The UUID always works as a fallback. See Sending messages overview.
Messenger supports sending images, videos, audio, and documents, but does not support
content.text captions with imageUrl, videoUrl, audioUrl, or documentUrl. Companion text
is discarded; send the description in a separate text request. See the caption support matrix.
Location/contact inputs use a readable text fallback. Replies forward the referenced provider message; rendering depends on the provider/client. See Content Types.
Next steps
- Supported content types on Messenger
- Interactive messages — buttons, list, and CTA URL