Clepher
MessagingAutomate Clepher Messenger bots, looking up subscribers, dispatching flows and cards, and managing tags and custom fields. Agents keep Messenger audiences segmented and react to capture-tool submissions.
What This Integration Enables
Clepher, formerly Clever Messenger, is an audience platform first and a chatbot second. Almost every operation in this connector is about who somebody is rather than what they said: subscribers with custom fields, tags that define segments, flows that branch on those tags, and capture widgets that add people to the list. If you are looking for a support inbox, this is the wrong tool. If you are running lifecycle marketing on Messenger, the tag is your primary object and everything else is downstream of it.
FlowRunner agents work that model directly. They resolve a person from an identifier captured elsewhere with Find Subscriber By Evidence, or from a Messenger profile ID, and read the full record including custom fields and tags. They write persistent values with Set Subscriber Custom Field and clear expired ones with Unset Subscriber Custom Field. They attach and detach tags to move somebody between lifecycle stages. They dispatch either a complete flow with temporary air variables carrying per-recipient detail, or a single card out of a flow when only one step needs re-sending. They can bundle several of these into one request with Run Subscriber Actions, list the growth widgets on the bot and whether each is published or still a draft, and whitelist a domain so Messenger will accept capture tools served from a new site.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Purchase Tags the Subscriber and Sends the Right Confirmation
An order completes in WooCommerce. The agent matches the buyer to their Messenger profile with Find Subscriber By Evidence using the email on the order. It writes the order number and plan into custom fields with Set Subscriber Custom Field, attaches the customer tag, and finishes with Send Flow To Subscriber carrying the order details as air variables. Because air variables exist only for that dispatch, the order number personalizes the message without becoming a permanent field on the record.
Resolving a CRM Contact Before Anything Is Sent
A campaign is about to target a list assembled in HubSpot, but the list is keyed on email and Clepher is keyed on Messenger profiles. The agent runs Find Subscriber By Evidence for each contact, keeps the ones that resolve, and reports the ones that do not so the team knows the reachable size of the audience before committing to it. The unresolved contacts become a separate list to reach on another channel rather than silent gaps in a send.
Re-sending One Step Instead of the Whole Sequence
A customer reports that they never received their booking confirmation, though the rest of the onboarding sequence arrived. The agent finds the flow with List Flows, finds the confirmation step with List Flow Cards, and calls Send Card To Subscriber for that one card. The customer gets the missing message. They do not get put back through five steps they already completed, which is what a re-enrollment would have done.
Human-in-Loop Highlight
In Clepher, a tag is not a label. It is the thing broadcasts target and the thing flows branch on, so changing tags changes what the platform will say to a person for months afterward, and Detach Tag From Subscriber leaves no trace of the segment somebody used to belong to. That makes bulk re-segmentation the operation FlowRunner will not run unsupervised. When a sync proposes tag changes across more than one subscriber, the agent stops and treats it as a human-in-the-loop decision: it posts the diff to the marketing owner with counts and named examples. "Reconciling billing against Clepher: 214 subscribers gain the paid tag, 38 lose the trial tag, 6 matched by phone number rather than email. Attaching is additive. Detaching removes those 38 from every broadcast keyed on trial. Apply, apply only the additions, or hold?" The owner answers, and only then does the agent run the moves. There is a second reason to stop here. Run Subscriber Actions applies a batch in one request, and Clepher documents that Send Flow and Send Card interrupt everything queued after them, so a composite assembled in the wrong order both sends a message and silently drops the steps behind it. A person sees the ordered list before it executes.
Agent Capabilities
16 actionsBots
1- List Bots Returns every bot in the Clepher account. This is the only operation that uses the account-level API key, since each bot carries its own separate key that the rest of the operations require. Used to discover which bots exist before configuring bot-scoped connections.
Subscribers
4- List Subscribers Returns all subscribers of the bot the configured key belongs to, including name, profile picture, custom field values, and tags. Clepher documents no pagination for this endpoint, so it returns the full audience in one response.
- Find Subscriber By Profile ID Looks up a single subscriber by their Messenger profile ID and returns the full record with custom fields and tags. Used to confirm somebody is subscribed and read their stored data before deciding what to send.
- Find Subscriber By Evidence Matches a subscriber against any identifying value already on their record, such as an email address, phone number, or custom field value. Used when a flow only knows a detail captured in another system and needs to resolve it to a Clepher profile.
- List Tagged Subscribers Returns the subscribers currently carrying one or more tags, along with which tags each holds. Used to export a segment for a broadcast or reconcile Clepher tags against another system's audience.
Flows and Cards
2- List Flows Returns the flows built for the bot, with the message type and Facebook message tag each is configured to send under. Flow IDs from this list are what the send operations expect.
- List Flow Cards Returns the individual cards that make up a flow. A card is the smallest unit Clepher can dispatch on its own, so listing them lets a flow send one specific step instead of restarting the sequence.
Capture Tools
1- List Capture Tools Returns the growth widgets configured on the bot, such as Send To Messenger buttons, checkbox plugins, and the customer chat widget, with whether each is published or still a draft. A subtype filter narrows Send To Messenger widgets to a single presentation style.
Subscriber Actions
7- Send Flow To Subscriber Schedules a complete flow for delivery to one subscriber. Air variables are temporary values that exist only for this dispatch, which makes them the right way to pass order numbers or appointment times into a templated flow without writing them to the record.
- Send Card To Subscriber Sends one specific card from a flow instead of the whole sequence. Used to re-send a single confirmation or reminder without putting the subscriber back through every step.
- Attach Tag To Subscriber Applies a tag so the subscriber joins the corresponding segment. Tags are how Clepher targets broadcasts and branches flows, so this is how an external event such as a purchase changes what the bot says next.
- Detach Tag From Subscriber Removes a tag, taking the subscriber out of that segment. Paired with an attach to move somebody between lifecycle stages, such as dropping a trial tag once a paid plan starts.
- Set Subscriber Custom Field Stores a value in a named custom field on the subscriber's record. Unlike air variables the value persists, so later flows and broadcasts can reference it. This is where CRM data such as a plan name or renewal date belongs.
- Unset Subscriber Custom Field Clears a named custom field on a subscriber's record. Used to retire data that has expired, such as a redeemed coupon code, so downstream flows stop branching on a stale value.
- Run Subscriber Actions Applies several actions to one subscriber in a single request, for cases where separate calls would mean multiple round trips. Order matters, because Send Flow and Send Card interrupt everything queued after them and must come last in the list.
Domains
1- Whitelist Domain Adds a domain to the bot's whitelist so Messenger allows it to host capture tools and receive linked traffic. Facebook rejects widgets served from an unlisted domain, so this runs before a Send To Messenger button is deployed on a new site.
Frequently Asked Questions
What can FlowRunner do with Clepher?
FlowRunner agents can run List Bots, List Subscribers, and Find Subscriber By Profile ID in Clepher, plus 13 more actions.
Does connecting Clepher to FlowRunner require OAuth?
No. Clepher connects to FlowRunner with an API key, no OAuth flow required.
Can Clepher trigger a FlowRunner workflow automatically?
Clepher doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Clepher
$100 in credits. No card required. Connect in minutes.