ChatForma

Automate ChatForma messenger chatbots, broadcasting to segments, replying inside live-chat dialogs, and managing subscriber variables. Agents start a flow the moment a bot event fires.

1 trigger 23 actions API key available

ChatForma website ↗ Platform Documentation ↗ Capability data verified 2026-08-02

On Form Submission fires when a subscriber completes a bot form

Agent reads the question and answer pairs from the delivered payload

Agent writes the answers onto the subscriber with Set Subscriber Variable so later bot messages can personalise on them

Agent reads List Segments and decides which segment those answers place the subscriber in

Agent calls Add User To Segment to move them into it

Before any broadcast goes to that segment, a person confirms which segment ID is being sent to

What This Integration Enables

ChatForma is messenger marketing, not a support desk. Everything in it points the same way: bots have subscribers, subscribers belong to segments, segments receive broadcasts, and per-subscriber variables make each of those broadcasts read as if it were written for one person. The live-chat dialog operations are the escape hatch, the place where a human steps out of the bot script and answers directly. That distinction matters when you decide what to automate here, because the risk profile of a marketing list is not the risk profile of a support queue. Nobody complains about a slow reply to a broadcast. They complain about receiving one.

FlowRunner agents use this connector in two directions. Inbound, a form submission becomes structured data that lands in a CRM, a spreadsheet or a support queue while the subscriber is still in the conversation. Outbound, the agent maintains the audience: reading form answers, writing them into bot variables, and moving people between segments so the list stays true without anyone exporting a CSV. What FlowRunner adds on top is that the agent knows which of those operations it should not perform alone. Building an audience is safe. Sending to it is not, and that is where human-in-the-loop belongs.

Without FlowRunner

Form answers stranded in the bot Submissions sit inside ChatForma with nothing downstream reading them

Segments maintained by hand Membership is exported, edited and re-imported, so it is stale by the time it is used

One field between a segment and everyone Nothing stands between the intended audience and the entire subscriber list

With FlowRunner

Answers become routing data Each submission writes subscriber variables and places the person in the right segment

Membership follows the conversation Segment membership reflects what the subscriber actually told the bot

Audience confirmed before dispatch The recipient set is resolved and shown to a person before the job is queued

Use Case Scenarios

Form submission to CRM without leaving the chat

A subscriber completes a qualification form inside the bot. On Form Submission fires with their profile and the full list of question and answer pairs. The agent creates a record in Airtable with the answers mapped to columns, writes the same values back onto the subscriber with Set Subscriber Variable so the bot can reference them later, and adds the subscriber to the segment that matches their answers. The lead is logged, personalised and routed before the person has closed the messenger window.

AI-assisted replies inside a live dialog

A subscriber breaks out of the bot script and asks something the script does not cover. The agent calls List Dialog Users to find dialogs waiting on a reply, then List Dialog Messages to read the exchange, using the is_client_message flag to separate what the subscriber said from what the bot said. It drafts a reply from that context and posts it with Send Dialog Message, which the subscriber sees as an operator response rather than a broadcast. When the draft touches pricing, cancellation or anything the agent is not confident about, it stops and hands the drafted reply to a person instead of posting it.

Lifecycle segments maintained by events elsewhere

A payment succeeds in Stripe. The agent calls Set Subscriber Variable to record the plan name and renewal date against the subscriber, then Add User To Segment to move them into the paying segment and Remove User From Segment to take them out of the trial segment. No export, no manual list hygiene, and the next broadcast to either segment reaches the right people because the membership was updated by the event that changed it.

Human-in-Loop Highlight

The gate here is Broadcast To Segment, and the specific reason is segment ID 0. Passing a real segment ID sends to that segment. Passing 0 sends to every subscriber of the bot. It is one character of difference between a targeted announcement and a message to your entire list, and once the dispatch job is queued there is no unsend. So a FlowRunner agent builds the broadcast completely and then stops: it resolves the target with List Segments, counts the audience with List Segment Users, and posts to the marketing channel: "Broadcast ready for segment 12, Trial day 7. Recipient count and message preview attached. Confirm this segment before I queue it, and tell me explicitly if you meant segment 0, which is every subscriber on this bot." A person reads the segment name and the preview, taps approve, and the agent queues the job. The same gate applies to Broadcast Prepared Message To Segment, and to Delete Variable, which removes a variable definition along with every subscriber value stored against it. The agent is happy to assemble any of those. It will not be the one that pulls the trigger.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

23 actions

Account

Verify API Key Validates the configured ChatForma API key and returns the email address of the account it belongs to. Used as a connection health check, and to confirm which ChatForma account a flow is acting on before it writes anything.

Bots and Forms

List Bots Returns every chatbot in the account with its numeric identifier, title and messenger platform. Most other operations need a bot ID, so this is the usual first call in a flow.
List Forms Returns the forms defined on a bot. A form ID is required to subscribe to the trigger or to inspect a form's field list.
Get Form Fields Returns a sample notification payload for a form, showing the exact question and answer fields ChatForma will deliver on submission. Used to map fields correctly before the first live submission arrives.

Subscribers

List Bot Users Returns the subscribers of a bot with their chat ID, name and subscription timestamps, paginated. A subscriber carrying a non-null deleted_at value has unsubscribed, which is what an audience-hygiene flow checks for.

Segments

List Segments Returns the subscriber segments defined on a bot. Segment IDs are what the membership and dispatch operations expect, so the agent resolves the segment by name here rather than carrying a hard-coded ID.
List Segment Users Returns the subscribers currently in a specific segment. Used to audit membership, and to produce the recipient count a person sees before approving a broadcast.
Add User To Segment Adds an existing bot subscriber to a segment so they receive that segment's broadcasts. The subscriber must already exist on the bot.
Remove User From Segment Removes a subscriber from a segment so they stop receiving its broadcasts. The subscriber stays subscribed to the bot itself.

Messaging

Broadcast To Segment Queues a free-form text broadcast to every subscriber in a segment and returns the dispatch job with its delivery counters. Segment ID 0 reaches all of the bot's subscribers, which is why this operation is the one an agent should hold for approval.
Send Message To Subscriber Queues a free-form text message to a single subscriber and returns the dispatch job. Supply a start date to schedule it for later, or leave it empty to send immediately.
List Prepared Messages Returns the reusable messages built in the ChatForma bot editor. Their IDs are what the prepared-message send operations expect when the content carries buttons or media that plain text cannot express.
Send Prepared Message To Subscriber Sends a message designed in the bot editor to a single subscriber. Used when the content is rich rather than plain text.
Broadcast Prepared Message To Segment Broadcasts a designed message to every subscriber in a segment, immediately or at a scheduled start date. Carries the same audience risk as a text broadcast and belongs behind the same approval.

Dialogs

List Dialog Users Returns the subscribers with an open live-chat dialog, paginated. Used to find conversations waiting on a human reply.
List Dialog Messages Returns the message history of a single dialog, paginated, newest page first. The is_client_message flag separates subscriber messages from bot and operator replies, which makes it suitable for feeding conversation context to an AI step.
Send Dialog Message Posts an operator reply into an existing dialog, so the subscriber sees a human response rather than a broadcast. Paired with the read operations above, this is how an AI-assisted support desk answers without pretending to be a bot.

Variables

List Variables Returns the variables defined on a bot with their name and data type. Variables store per-subscriber values such as a plan name or an order number and drive personalisation inside bot scripts.
Create Variable Defines a new variable on a bot so subscriber-specific values can be stored against it. The name must be unique within the bot and the type must be String, Number, or Boolean.
Delete Variable Permanently removes a variable definition along with the values stored against it for every subscriber. Bot scripts referencing it stop resolving, which makes this a write worth confirming.
Get Subscriber Variable Reads the value a specific subscriber has stored against a bot variable. Used to branch a flow on something the bot collected earlier.
Set Subscriber Variable Writes a value into a bot variable for a specific subscriber so later messages personalise on it. Values are submitted as text and coerced by ChatForma to the variable's declared type.

Webhooks

List Webhook Subscriptions Returns the webhook subscriptions currently registered for a form with their IDs and target URLs. Useful for auditing which external endpoints receive a form's submissions, including subscriptions created outside FlowRunner.

Triggers

1 triggers

Event Triggers

On Form Submission Fires when a subscriber submits the selected ChatForma form, delivering the submitting subscriber's profile together with the full list of question and answer pairs they provided. FlowRunner registers the notification subscription when the flow is enabled and removes it when the flow is disabled, so the subscription lifecycle follows the flow rather than needing separate cleanup. This is the entry point for lead capture, qualification routing and any workflow that should start while the subscriber is still in the conversation.

Frequently Asked Questions

What can FlowRunner do with ChatForma?

FlowRunner agents can run Verify API Key, List Bots, and List Forms in ChatForma, plus 20 more actions.

Does connecting ChatForma to FlowRunner require OAuth?

No. ChatForma connects to FlowRunner with an API key, no OAuth flow required.

Can ChatForma trigger a FlowRunner workflow automatically?

Yes. ChatForma supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with ChatForma

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us