Facebook Messenger
Connect a Facebook Page and your flow can answer Messenger conversations around the clock, from the same AgentFlow you use everywhere else.
Set the Page up first: Facebook credentials. The node reference lives at Facebook trigger and Facebook tool.
What Facebook flows can do
- Answer messages — text, images, video, audio and files people send your Page.
- Offer buttons — up to three tappable choices; the tapped button comes back to the flow as a value you can branch on, instead of free text you have to interpret.
- Follow ad clicks — when someone arrives from a Click-to-Messenger ad, the ad ID reaches the flow so you can tailor the greeting and attribute the lead.
- Step aside for a human — when an operator answers from the Page inbox, Flowera notices and stops replying. See Manual mode.
Trigger events
| Event | Fires when |
|---|---|
| Messages | Someone sends your Page a message |
| Button clicks | Someone taps Get Started, a menu item, or a button your flow sent |
| Ad / link referrals | Someone opens the chat from a Click-to-Messenger ad or an m.me link without typing yet |
Subscribe only to the events a flow should handle. A flow listening to everything runs — and bills — on every event.
Two limits worth knowing before you build
The 24-hour window
You may reply to a person for 24 hours after their last message. The clock restarts every time they message you, tap a button, comment on a Page post, or click a Click-to-Messenger ad.
Outside that window, Flowera cannot message them at all. Meta retired most of the message tags that used to allow it in April 2026, and the one remaining route (the Human Agent tag, which extends the window to 7 days) requires a separate Meta approval this app does not hold. So design flows to finish the conversation while it is live — do not plan on a follow-up tomorrow.
Names yes, pictures no
Flowera can read the person's name, but not their profile picture and not a username.
The name comes from the conversation itself. The profile picture needs a separate Meta permission
("Business Asset User Profile Access") this app has not been granted, and Messenger has no username
for Page conversations at all — so senderUsername is always empty.
Treat senderName as best-effort: Meta does not always have a name to give, so give your flow a
fallback rather than assuming it is filled.
What Facebook flows cannot do yet
- Page comments. Replying to, hiding, or deleting comments on Page posts needs Meta permissions this app has not been granted. Only Messenger conversations are supported.
- Messaging first. A person must start the conversation. There is no way to open a thread from Flowera.
How it compares
| Customer identity | Name (best-effort), no picture | @username | Phone number + verified name |
| Reply window | 24 hours, no extension | 24 hours | 24 hours, templates reopen it |
| Comments | Not supported | Supported | N/A |
| Buttons | Up to 3 | Generic template | Interactive lists and buttons |
| Delivery states | sent → delivered → read | sent → read | sent → delivered → read |