Facebook Messenger
CommunicationConnect AI agents to Facebook Messenger through your Facebook Pages. Agents send text, media, button and generic templates, quick replies, and typing indicators, read conversations, and configure the page's greeting, Get Started button, and persistent menu.
What This Integration Enables
Messenger is not an open channel; it is a channel with rules. Recipients must message your Page first, standard replies are only allowed inside the 24-hour window after the user's last message, out-of-window sends require an eligible message tag, and public use of pages_messaging requires Meta App Review. Most teams either ignore the channel or violate its terms by accident. FlowRunner treats the rules as workflow logic: agents answer fast inside the window, collect structured responses with rich templates, and route everything else to the paths Meta actually permits. - Send text, media, button templates, carousel cards, and quick replies through your Page - Track the 24-hour window per conversation and branch behavior when it closes - Read conversations and messages to resolve PSIDs and thread context - Personalize with user profile fields where permissions and privacy settings allow - Configure the Page's greeting, Get Started button, and persistent menu as code - Make automation feel human with typing indicators and read receipts
Without FlowRunner
With FlowRunner
Use Case Scenarios
The order-status question answered in seconds
A customer messages the Page. The flow resolves their PSID through List Conversations, matches them to a contact in [HubSpot](/integrations/hubspot), and pulls the open order. Send Sender Action shows typing, then Send Button Template delivers the status with a tracking link button and a postback button for "something's wrong". The wrong-path postback opens a ticket in [Zendesk](/integrations/zendesk) with the full thread attached, and the customer never repeats themselves.
Lead capture that starts with Get Started
The Page's onboarding is configured by flow: Set Greeting welcomes by first name, Set Get Started Button fires the qualification flow, and Set Persistent Menu keeps pricing and support one tap away. When someone taps Get Started, Send Quick Replies walks them through three structured questions, the answers write to the CRM, and qualified leads alert the sales channel in [Slack](/integrations/slack) with the conversation snippet attached.
The product drop announced as a carousel
For customers who messaged about availability, the flow builds a Send Generic Template carousel: up to ten cards with product images, prices, and buy buttons, each assembled from live catalog data. Sends respect each conversation's window state, in-window customers get the carousel immediately, and everyone else routes to the follow-up queue instead of into a policy violation. Replies and taps flow back into the same thread-aware pipeline.
Human-in-Loop Highlight
The riskiest write in this connector is the out-of-window send. Once the 24-hour window closes, Send Text Message only goes through under a message tag, and the most commonly eligible one, Human Agent, is a specific claim to Meta: a human is handling this conversation. Misuse tags at scale and the consequence is not a bounced message; it is Meta reviewing your Page's messaging access, which is the whole channel. So FlowRunner makes the tag true by construction. When a conversation's window has expired, the agent does not send. It packages the thread, the customer context, and a drafted reply into a review queue, and a person reads, edits, and releases the message, which then goes out tagged Human Agent because a human agent actually approved it. Inside the window, automation runs free and fast. Outside it, the platform's rule and FlowRunner's gate are the same thing: a person in the loop.
Agent Capabilities
15 actionsMessaging
6- Send Text Message Sends a plain text message to a user via the Page, addressed by PSID. Standard messaging applies inside the 24-hour window; outside it, an eligible message tag such as Human Agent is required. Public use requires pages_messaging Advanced Access through Meta App Review.
- Send Media Message Sends an image, audio, video, or file attachment fetched from a public URL, with an option to receive a reusable attachment_id for future sends. Subject to the same window and access rules as text.
- Send Button Template Sends text with up to three tappable buttons, each opening a link or sending a postback payload to your webhook. The building block for status updates with next actions attached.
- Send Generic Template Sends a carousel of up to ten horizontally scrollable cards, each with title, subtitle, image, default action, and buttons. The format for product drops and multi-option answers.
- Send Quick Replies Sends a message with up to thirteen quick reply chips that disappear once tapped, returning their payload to your webhook. The structured-answer collector behind qualification flows.
- Send Sender Action Sends typing on, typing off, or mark seen. Sender actions do not count as messages, and they make automated conversations feel attended.
Conversations
3- List Conversations Lists the Page's Messenger conversations with participants, last update, latest snippet, and unread count. The source of PSIDs and thread IDs for everything else.
- Get Conversation Messages Lists the messages in a conversation with sender, recipient, text, time, and attachments. Only recent history is accessible through the API.
- Get User Profile Retrieves a user's first name, last name, profile picture, locale, and timezone where permissions and privacy settings allow. The personalization read for active conversations.
Page Profile
5- Get Messenger Profile Retrieves the Page's configured greeting, Get Started payload, and persistent menu, the welcome experience users see in the thread.
- Set Get Started Button Configures the Get Started button whose tap sends your chosen payload to the webhook, the entry point of every onboarding flow.
- Set Greeting Sets the greeting text shown before a conversation starts, with personalization tokens such as the user's first name supported.
- Set Persistent Menu Sets the always-available menu of postback, link, and nested items, one menu object per locale.
- Delete Messenger Profile Fields Removes greeting, Get Started, or persistent menu configuration. Deleting Get Started also clears the persistent menu, which depends on it.
Pages
1- List My Pages Lists the Pages the authenticated user manages with ID, name, and category. The messaging actions resolve each Page's access token behind the scenes.
Frequently Asked Questions
What can FlowRunner do with Facebook Messenger?
FlowRunner agents can run Send Text Message, Send Media Message, and Send Button Template in Facebook Messenger, plus 12 more actions.
Does connecting Facebook Messenger to FlowRunner require OAuth?
Yes. Facebook Messenger connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Facebook Messenger trigger a FlowRunner workflow automatically?
Facebook Messenger doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Facebook Messenger
$100 in credits. No card required. Connect in minutes.