Sendbot

Automate the Sendbot AI chatbot platform for WhatsApp and web, managing workspaces and bots and driving chat sessions end to end. Agents keep conversational flows current as the underlying content changes.

35 actions API key available

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

A product change means the bot needs a new qualifying question

Agent applies the change with Edit Flow using a natural-language instruction

Agent compares Get Bot Draft against Get Bot to confirm what actually changed

Agent rehearses the edited path with Start Preview Session, which does not persist results

Owner receives the rehearsal transcript and the credit balance from Get Billing Balance

Owner approves before the edited flow becomes what visitors meet

What This Integration Enables

Sendbot is the one platform in this category where the agent can write the bot. Generate Flow scaffolds a whole conversation from a plain-language brief. Edit Flow applies a natural-language change to a flow that already exists, at whatever scope the instruction implies, including every message in it. Start AI Agent hands a task to Sendbot's own agent rather than a fixed flow. That is a different proposition from administering a chatbot, and it is worth naming plainly, because a capability that authors customer-facing copy needs a different governance posture from one that reads a contact list.

The rest of the surface supports that. Agents list, read, create, update, and delete workspaces, which are the top-level container owning bots, members, and billing. On bots they list, read, create, and partially update, import a bot from an exported definition to clone a template or restore a backup, and delete one outright. They also resolve the bots linked from another bot's flow to audit a chain, look up the bot published on a custom domain, check a public ID is free before assigning it, and read the unpublished draft separately from the published version.

Sessions are where the conversation actually lives, and agents drive them end to end. They start a session with prefilled variables and a channel tag, send visitor messages, and continue it turn by turn. They pause it so a person can take over with state preserved, then resume from exactly where it stopped. They write flow variables mid-conversation from an external system, switch the bot driving a session to route a visitor from triage to a specialist, and delete a session to honor a data deletion request. On the commercial side they read the credit balance, itemized usage, aggregated stats, transaction history, and the current per-model price list, and they read the available AI models at runtime rather than hardcoding names.

Without FlowRunner

Bot edits mean opening the builder A one-line wording change waits on whoever owns the flow diagram

Machine-written copy ships unread An AI edit touches every message and nobody rehearses the result

Credit burn discovered on the invoice A bulk run exhausts the balance partway through and fails in the middle

With FlowRunner

Edits are instructions a flow can carry Edit Flow applies a natural-language change from whatever system noticed the need

Every generated change gets a rehearsal A preview session runs the edited path against the draft without persisting results

Balance is checked before the run, not after Get Billing Balance gates a bulk job so it stops early instead of halfway

Use Case Scenarios

Routing a Visitor Without Restarting Them

A visitor starts on the general triage bot and turns out to have a billing question. Rather than dropping them into a new conversation, the flow calls Set Session Bot to switch the bot driving the existing session to the billing specialist. Everything the visitor already said stays on the session, and the specialist bot picks up from there. The visitor does not re-enter their order number, which is the single most common reason people abandon a chat.

Human Handover With the State Held Open

A session hits a request the bot should not answer. The agent calls Pause Session, which stops the bot replying while preserving the conversation state, and opens a Slack thread with the transcript for the on-duty operator. When the operator is done, the agent calls Resume Session and the bot continues from the exact point it stopped. Sendbot's own pause and resume primitives are what make this a genuine handover rather than a restart, and FlowRunner is what decides when it should happen.

Credit Burn Reported Before It Becomes a Surprise

Weekly, the agent pulls Get Billing Usage Stats for the rollup and Get Billing Usage for the line items showing what each session and AI call cost. It reads the current rates with Get Billing Pricing and writes the result into Google Sheets with a note on which bots drove the change. Before any bulk job, a separate check reads Get Billing Balance and stops the run up front if the balance will not cover it, instead of discovering the limit halfway through a batch.

Human-in-Loop Highlight

Edit Flow is the operation that decides how this connector has to be wired. It takes a natural-language instruction and applies it to a bot's flow, and Sendbot's own documentation gives changing the tone of every message as an example of its reach. That means one call can rewrite what a business says to every visitor, in copy no person has read, on a platform where the bot is reached through public links and embeds. FlowRunner does not let that go out unattended, and it does not have to guess how to check it, because Sendbot ships the instruments. The agent runs the edit, compares Get Bot Draft against Get Bot to see precisely what is pending, then calls Start Preview Session, which runs against the unpublished draft and does not persist results, and walks the changed path with Continue Session as if it were a visitor. It hands the whole thing to the owner as a human-in-the-loop decision: "Edit Flow rewrote 11 of 14 messages to add the new qualifying question. Rehearsal transcript attached. The new wording asks for company size before the pricing answer. Release this to visitors, revise the instruction, or discard the draft?" A person reads what the machine wrote before a customer does. The same posture covers the two deletes on this connector, for the same reason rather than a different one. Delete Bot removes the bot and its published version, so every embed and public link stops working immediately. Delete Workspace takes the bots, sessions, and results inside it. Neither is restorable through the API.

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

35 actions

Workspaces

List Workspaces Returns the workspaces the token can access. Workspaces are the top-level container owning bots, members, and billing, so this is the usual first call when a flow needs to find where a bot should be created. Cursor-paginated.
Get Workspace Retrieves a single workspace with its profile and plan details. Used to confirm which subscription tier a workspace is on before a flow creates bots or starts sessions that consume credits.
Create Workspace Creates a new workspace to hold bots, members, and billing. Sendbot does not publish the full body schema, so the name is exposed directly and any other documented fields are merged into the request.
Update Workspace Applies a partial update to a workspace, changing only the supplied fields. Documented fields are passed as a key-value object because the full schema is not published, and anything omitted is left untouched.
Delete Workspace Permanently deletes a workspace. The bots, sessions, and results it owns go with it and cannot be restored through the API.

Bots

List Bots Returns the bots the token can access, optionally scoped to one workspace, cursor-paginated with a page size of 1 to 500. The overall count is returned only when explicitly requested.
Get Bot Retrieves the published definition of a single bot including its groups, settings, and theme. This is the live version a visitor sees, as distinct from the unpublished draft.
Create Bot Creates a new bot inside a workspace. The workspace and name are exposed directly, with the flow definition, theme, and settings merged in through additional fields since the full schema is not published.
Update Bot Applies a partial update to a bot, changing only the supplied fields. The safe way to adjust one setting such as a name or theme value without rewriting the flow definition.
Delete Bot Permanently deletes a bot together with its published version. Any embed or public link pointing at it stops working immediately.
Import Bot Creates a bot from an exported definition, which is how a flow clones a template between workspaces or restores a backup. The exported JSON is passed as the definition.
Get Linked Bots Resolves the bots linked from another bot's flow, so an automation can follow a jump between flows and audit the whole chain.
Get Bot By Domain Looks up the bot published on a custom domain. Used when an inbound event carries only the site the visitor was on and the flow needs the bot ID first.
Check Public ID Availability Checks whether a public ID is free before it is assigned. Public IDs form the shareable chat URL and must be unique, so this runs first in any flow that renames or provisions bots.
Get Bot Draft Retrieves the unpublished draft holding edits not yet released to visitors. Compared against the published definition to detect pending changes before an automated publish or review step.

Sessions

Start Chat Session Starts a session and returns the first batch of messages plus the input the bot is waiting on. Every field is optional: identify the bot by ID or pass an inline definition, seed with prefilled variables, tag the channel, or register the session without generating a reply. The response carries the session and result IDs the other session actions need.
Send Chat Message Sends a visitor message into the chat endpoint and returns the bot's reply, with the session and message exposed directly and any other documented fields merged in.
Start Preview Session Starts a session against a bot's unpublished draft so a flow can regression-test changes before they go live. Preview sessions do not persist results.
Continue Session Advances an existing session by submitting the visitor's next answer and returns the bot's replies. This is what a long-running conversation loop calls repeatedly.
Pause Session Pauses a session so the bot stops replying while a human agent takes over. Conversation state is preserved so the session can be handed back exactly where it stopped.
Resume Session Resumes a paused session and returns control to the bot from the point it stopped. Used to close a human handover once an agent has finished.
Delete Session Deletes a chat session and the conversation state held against it. Used to honor a data deletion request or clear test sessions created by an automated check.
Update Session Applies a partial update to a session, for example writing flow variables mid-conversation from an external system.
Set Session Bot Switches the bot driving an existing session, which is how a routing flow hands a visitor from a triage bot to a specialist one without losing the conversation.

Billing

Get Billing Balance Returns the credit balance available to the account. Checked before a bulk run so a flow can stop early rather than failing partway through when credits are exhausted.
Get Billing History Returns billing transactions such as top-ups and charges, cursor-paginated. Used to reconcile Sendbot spend against an internal ledger on a schedule.
Get Billing Usage Returns itemized consumption records showing what each chat session and AI call cost, for when the underlying line items matter rather than a rollup.
Get Billing Usage Stats Returns aggregated usage statistics for the account, suitable for a scheduled report or a threshold alert on credit burn.
Get Billing Pricing Returns the current price list including the per-model rates charged for AI calls. Used to estimate the cost of a run before starting it, or to surface pricing inside an internal tool.

AI

List AI Models Returns the AI models available to the account. The catalogue changes as providers are added, so it is read at runtime rather than hardcoded, and the same endpoint backs the model selectors on the AI actions.
Generate Flow Generates a complete bot flow from a natural-language brief, scaffolding a whole conversation from a description instead of building it block by block.
Edit Flow Applies a natural-language edit to an existing bot flow, for example adding a qualifying question or changing the tone of every message.
Start AI Agent Starts an AI agent run, letting Sendbot's agent work a task autonomously rather than following a fixed flow.
Save AI Memory Writes an entry into the AI memory store so later runs can recall facts learned in earlier conversations, such as a customer's plan or preferences.
Generate Title Generates a short descriptive title from supplied text, which is how Sendbot labels conversations and generated flows. Used to turn a raw transcript into a readable subject line for a ticket or a report row.

Frequently Asked Questions

What can FlowRunner do with Sendbot?

FlowRunner agents can run List Workspaces, Get Workspace, and Create Workspace in Sendbot, plus 32 more actions.

Does connecting Sendbot to FlowRunner require OAuth?

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

Can Sendbot trigger a FlowRunner workflow automatically?

Sendbot doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Sendbot

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

Start Building Free Talk to us