Chatfuel
CommunicationRe-engage Chatfuel subscribers from your flows. Agents push existing bot blocks and flows to individual users on Messenger, Instagram, and WhatsApp, deliver updates outside the 24-hour window with approved message tags, and sync subscriber attributes from other systems.
What This Integration Enables
A Chatfuel bot is a conversation waiting for a reason. It answers well when a subscriber writes in, but the events worth messaging about, a shipped order, a cleared payment, a booked meeting, happen in systems the bot has no view into. This integration is the bridge for that: FlowRunner agents watch the rest of the stack and use Chatfuel's Broadcasting API to push existing blocks and flows to individual subscribers the moment something happens, on Messenger, Instagram, or WhatsApp. - Re-engage a subscriber with a specific block or flow when an event fires in another system - Deliver time-sensitive updates outside the 24-hour window using approved Messenger message tags - Sync CRM, store, and payment data into subscriber attributes, and trigger a flow to react to the new values The API surface is deliberately narrow, three send-side operations and no reads, which makes discipline on the send path the whole game. FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) step sits exactly there. A note on the division of labor: the conversation design stays in Chatfuel. The blocks and flows your team built, the quick replies, the galleries, the branching logic, all of it remains exactly where it is. FlowRunner does not compose messages for this channel; it decides when an existing block should reach a specific subscriber, and it supplies the attribute data that makes the block render personally. That split keeps marketers in control of what subscribers see while agents control the timing that Chatfuel alone cannot know.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The order confirmation that arrives where the customer actually is
A buyer who found the store through the Messenger bot completes checkout in [Shopify](/integrations/shopify). The agent writes the order details onto their profile with Set User Attributes, then delivers the confirmation block: Send Block if they chatted recently, Send with Message Tag under POST_PURCHASE_UPDATE if not. The customer gets the confirmation in the same channel where the relationship started, and the block can answer follow-up questions the way email never will.
Payment confirmed, bot updated, thank-you triggered
A payment succeeds in [Stripe](/integrations/stripe). The agent calls Set User Attributes to store the plan name and amount on the subscriber, and triggers the thank-you flow in the same call. From that point the bot's own logic can reference the plan in every future conversation: support answers, upsell paths, renewal reminders, all personalized from data that used to live only in the billing system.
Meeting reminders that cut no-shows
An invitee books through [Calendly](/integrations/calendly). The agent stores the meeting time as an attribute, and the day before, sends the reminder block with Send with Message Tag under CONFIRMED_EVENT_UPDATE, a legitimate use of the tag because the subscriber confirmed the event. The reminder lands in a channel people actually check, with the bot ready to handle a reschedule request on the spot.
Human-in-Loop Highlight
Send with Message Tag is the operation that can cost you the channel itself. Meta permits messages outside the 24-hour window only under tags that genuinely match the content, ACCOUNT_UPDATE, CONFIRMED_EVENT_UPDATE, POST_PURCHASE_UPDATE, and a promotional message dressed in an update tag violates policy. The penalty is not a bounced message; it is Meta restricting your page's messaging, which takes every subscriber relationship down at once. So FlowRunner agents apply tags only from an explicit mapping of event types to tags, and anything ambiguous stops: "Subscriber's window closed 3 days ago. Content is a restock notice for an item they viewed. No approved tag fits a promotional restock notice. Send nothing, or reroute to email?" A person makes that call. The agent never stretches a tag to force a delivery, because the downside is not one lost message but the whole bot.
Agent Capabilities
3 actionsMessaging
2- Send Block Sends an existing block or flow from your Chatfuel bot to a specific subscriber, targeted by block name, block or flow ID, or flow name, exactly one of the three. Subject to Messenger's 24-hour messaging window, which makes it the right operation for replies to recent activity. Can set user attributes in the same call.
- Send with Message Tag Sends a block or flow outside the 24-hour window under a Messenger message tag such as ACCOUNT_UPDATE, CONFIRMED_EVENT_UPDATE, or POST_PURCHASE_UPDATE. The tag must match the content; this is the operation this page's human gate exists for.
User Attributes
1- Set User Attributes Sets one or more attributes on a subscriber's profile without requiring them to tap a button, and can trigger a block or flow in the same call to react to the new values. The sync path that keeps the bot's picture of a subscriber current with the CRM, store, and billing system, and the safest operation in the connector, since it sends nothing on its own unless a flow is explicitly attached.
Frequently Asked Questions
What can FlowRunner do with Chatfuel?
FlowRunner agents can run Send Block, Send with Message Tag, and Set User Attributes in Chatfuel.
Does connecting Chatfuel to FlowRunner require OAuth?
No. Chatfuel connects to FlowRunner with an API key, no OAuth flow required.
Can Chatfuel trigger a FlowRunner workflow automatically?
Chatfuel doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Chatfuel
$100 in credits. No card required. Connect in minutes.