BotDistrikt
MessagingRead and reply to BotDistrikt bot users across WhatsApp, SMS, and messaging apps, manage user attributes, and schedule sends. Agents handle routine conversation and hand the thread to a person when it stops being routine.
What This Integration Enables
BotDistrikt's distinguishing feature is that the bot's working memory is a first-class object you can read. Get Bot User Context returns the conversational state the bot is holding for a person, which means an AI step in FlowRunner can pick up a conversation exactly where the bot left it instead of greeting somebody who is already three questions in. Very few conversational platforms expose that, and it changes what kind of automation is honest to build on top of one. The other half of the platform is channel reach: bot users arrive over WhatsApp, SMS, and messaging apps, and one reply action delivers to whichever one a given person is on.
FlowRunner agents read and create bot users, shaping list queries with BotDistrikt's LoopBack filter object rather than page and limit parameters. They reply as the bot with free text an AI step composed, by handing the conversation to an existing story, or with an approved WhatsApp template. They read and clear the conversational context. They write and remove per-user custom attributes, which is BotDistrikt's key-value store and the thing broadcast targeting reads, and they list the attribute definitions available in the workspace. They read the bot's configuration and connected channels, list its stories, tags, and broadcasts with publishing state, start a CSV export of the audience, and schedule a broadcast to a LoopBack-defined segment with immediate, fixed-time, per-user-timezone, or repeating delivery. They also manage outbound webhooks, which in BotDistrikt are not event subscriptions but definitions of calls the bot itself makes mid-story so a reply can depend on live data.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Continuing a Conversation Instead of Restarting It
A customer messages the bot on WhatsApp with a question the story does not cover. Rather than dropping them into a fallback, the flow calls Get Bot User Context to read what the bot already knows and where in the story they are. It feeds that to an AI step alongside the account record pulled from HubSpot, then delivers the composed answer with Send Bot User Reply using the Text type. The person gets an answer that references what they already told the bot, on the channel they were already using.
Greeting a New User and Creating the Lead
On New Bot User fires the first time somebody messages the bot. The agent reads the full record with Get Bot User, notes the channel it arrived on, creates the lead in the CRM, and replies with Send Bot User Reply using the Story type so BotDistrikt plays the proper onboarding sequence rather than a one-off message. Because the trigger baselines existing users on its first cycle without firing, turning this flow on does not replay months of history at the sales team.
Attribute-Driven Campaign With an Honest Unsubscribe
An outcome elsewhere in the business, a purchase or a renewal, writes an attribute onto the person with Add Bot User Attributes. A later broadcast targets that attribute through a LoopBack condition list and delivers in each user's own timezone. When somebody asks to stop hearing about that topic, the agent calls Delete Bot User Attributes, which removes them from every segment keyed on it. The opt-out is the same mechanism as the opt-in, so there is no separate suppression list to fall out of sync.
Human-in-Loop Highlight
Reset Bot User Context is the operation that looks harmless and is not. It clears the working memory the bot is holding for a person, which is the correct fix for somebody stuck mid-story and a destructive one for somebody who is simply thinking. Everything the conversation collected but has not yet written anywhere goes with it, and the person's next message starts from nothing. Compounding it, "stuck" in BotDistrikt is a LoopBack query, so a slightly wrong condition selects the wrong cohort and resets all of them in one pass. FlowRunner treats these as automation exceptions rather than as work to finish. The agent builds the shortlist, reads each candidate's context and story position, and routes the batch to the support lead as a human-in-the-loop decision: "7 users idle past the threshold in the booking story. User 4412 has a date and party size in context and stopped at payment. Two others have empty context. Reset all, reset only the empty ones, or send a nudge with Send Bot User Reply instead?" The lead answers per person or per group. There is a second call worth the same treatment for the same reason: Delete Outbound Webhook is permanent, and any story step that referenced it simply stops calling out, so the bot keeps talking while the data behind its answers quietly stops arriving.
Agent Capabilities
19 actionsBot Users
4- Get Bot User Retrieves a single bot user by numeric ID with the stored profile, the channel they arrived on, and any custom attributes the bot has collected. Used to enrich a flow with everything BotDistrikt knows about a person before deciding how to reply.
- List Bot Users Lists the bot users belonging to a bot. BotDistrikt runs on LoopBack, so results are shaped with a filter object supporting where, fields, order, limit, and skip rather than page and limit parameters.
- Create Bot User Creates a bot user on a bot. Only SMS and WhatsApp users can be created with phone numbers; users from other messaging apps are generated automatically when the person first messages the bot. Remaining profile fields are merged into the request as supplied.
- Send Bot User Reply Sends a reply as the bot, choosing Text for a message written in the flow, Story to hand the conversation to an existing BotDistrikt story, or WhatsApp Template for an approved template. Only the field matching the chosen type is used, so an AI step can compose the text and this delivers it on whichever channel the person is on.
Conversational Context
2- Get Bot User Context Returns the conversational context BotDistrikt is holding for a bot user, which is the working memory the bot uses to decide what to say next. Read it before an AI step so the model continues the conversation instead of restarting it.
- Reset Bot User Context Clears the conversational context held for a bot user, returning them to a clean slate on their next message. Used when a flow has finished a task and the bot should stop resuming an old story, or to recover somebody stuck mid-conversation.
Attributes
3- Add Bot User Attributes Writes custom attributes onto a bot user. Attributes are BotDistrikt's per-user key-value store and what broadcast targeting reads, so setting one is how a flow tags a person for a later campaign or records an outcome such as a purchase.
- Delete Bot User Attributes Removes named custom attributes from a bot user, which takes them out of any broadcast segment targeting that attribute. This is the counterpart to writing one, and the honest way to unsubscribe somebody from a campaign topic.
- List Attribute Definitions Lists the custom bot user attributes defined in the workspace. Called to discover available attribute names before writing one or referencing one inside a broadcast targeting expression.
Bot Configuration
3- Get Bot Retrieves a single bot by numeric ID with its configuration and connected channels. Used as a connection health check, or to confirm a bot exists before a flow starts writing users and broadcasts against it.
- List Bot Stories Lists the stories configured on a bot. Stories are the conversational flows BotDistrikt plays back, and their numeric IDs are what the reply and broadcast operations expect when sending a story rather than free text.
- List Bot Tags Lists the tags defined on a bot. Tags label bot users for segmentation, so this resolves a readable tag name into the ID a filter or targeting expression needs.
Broadcasts and Export
3- List Bot Broadcasts Lists the broadcasts created on a bot with their publishing state, from Unpublished and Scheduled through to Finished or Error. Used to check whether a campaign scheduled earlier actually went out, or to audit recurring broadcasts.
- Create Broadcast Schedules a broadcast to a segment of a bot's users. The broadcast object picks what is sent, a story, plain text, a card, an image, or an approved WhatsApp template, and the target is a LoopBack condition list selecting the audience. Delivery can be immediate, at a fixed time, in each user's own timezone, or on a repeating period.
- Export Bot Users CSV Starts a CSV export of a bot's users so the audience can be handed to a warehouse, an email tool, or an ad platform. BotDistrikt produces the file and the response reports where it can be collected.
Outbound Webhooks
4- Create Outbound Webhook Registers an outbound webhook on a bot. This is not an event subscription: it defines an HTTP call the bot itself makes part-way through a story so the reply can depend on live data, and the URL may embed conversation memory.
- Get Outbound Webhook Retrieves a single outbound webhook definition by numeric ID with the bot it belongs to and the method, URL, and query parameters the bot uses. Used to verify a definition before a story goes live.
- Update Outbound Webhook Applies a partial update to an outbound webhook definition. Only the supplied fields change, which makes it safe to repoint a bot at a new endpoint or rename a webhook without restating the rest.
- Delete Outbound Webhook Permanently removes an outbound webhook definition. Any story step that referenced it stops calling out, so the bot's stories are worth checking before deleting one still in use.
Triggers
1 triggersEvent Triggers
1- On New Bot User Fires when a new bot user appears on the selected bot, emitting the full bot user record so a flow can greet the person, create a CRM lead, or notify an agent. The first cycle records the users that already exist without firing, so history is never replayed; afterwards each new user fires once, oldest first, deduplicated by ID. The watched set can be narrowed with a LoopBack filter, for example to a single channel, and the polling interval is configurable down to 30 seconds.
Frequently Asked Questions
What can FlowRunner do with BotDistrikt?
FlowRunner agents can run Get Bot User, List Bot Users, and Create Bot User in BotDistrikt, plus 16 more actions.
Does connecting BotDistrikt to FlowRunner require OAuth?
No. BotDistrikt connects to FlowRunner with an API key, no OAuth flow required.
Can BotDistrikt trigger a FlowRunner workflow automatically?
Yes. BotDistrikt supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with BotDistrikt
$100 in credits. No card required. Connect in minutes.