Changelog

User-facing changes merged into the product each month. Some features roll out to organizations gradually; where a feature is in early access, the entry says so.

October 2026Copy Anchor Link

Subworkflows

• Subworkflows, a new project type: build a set of steps once, with a Start step for what it takes and Exit steps for its named ways out, and add it to any USSD, chatbot or automation project with a Subworkflow step. Its steps run inside each project, so they can show a USSD menu or send a chat message. See Subworkflows.
• Subworkflows are published as numbered versions. Each project stays on the version it chose until someone reviews the update on its step and publishes the project. Used by lists the projects that use one, and one in use is archived rather than deleted. See Versions and updates.
• Subworkflows don't count toward your plan's projects. Buni can add a Subworkflow step for any of your organisation's subworkflows.

Shared workflows

• Shared workflows: give an automation a Called by another flow trigger and end it with Return steps, and your USSD, chatbot and automation projects run it with a Run workflow step and use its answer in the same session. Build a client lookup or an access-token fetch once. See Shared workflows.
• Reuse the result answers repeat calls from a saved result for up to 60 minutes. Each call that runs counts as one automation run; a reused answer is free.

Integrations

• Capture response on an Integration node now works in USSD and chatbot projects, as it did in automations. A path reads the action's own result there, such as data for Google Sheets Read Rows. Republish to apply. See Capture response.
• Run in Configure Tool shows what each capture item would save from the result, so a wrong path shows before you publish. Capture items in Integration and API nodes can be named.
• Google Sheets: Find or Add Row updates the row whose key column matches a value, such as a caller's phone number, or adds one. Given an object, it changes only the cells it names. See Find or Add Row.
• Google Sheets: Read Rows has a hasHeaderRow switch that keys each row by its column names, and every read now numbers its rows as in the sheet.
• Test runs of Google Sheets actions now answer and write exactly as the published node does.
• Send in an API node no longer saves your other unsaved changes; Discard drops them as it should.

Chatbots

• A new Languages tab in project settings sets the language your flow is written in, whether a conversation follows the language people write in, and whether each contact's language is remembered. Republish to apply. See Language settings.
• Once you republish, tapping a button or quick reply no longer switches a conversation's language on any channel. Some taps arrive as a full English sentence, which could move a French conversation, and the contact's saved language, to English. A message matched by a keyword rule, or one the bot could not classify, no longer counts as English either. Flows can tell a tap from a typed message with {{requestAttributes.inputSource}}.
• In the web chat, a tapped quick reply now sends its value, as a button does, and the transcript still shows the label the visitor tapped.
• Built-in translations. Reply, Live Chat and Form nodes have a Translations tab. Each message is sent in the conversation's language when it has a translation, and in the original otherwise. A translation can use only its original's variables, and button values never change. See Translating your messages.
• Languages settings list the languages a project serves, and which one other languages get instead of the original.
• AI Agent nodes are told the conversation's language, and the chatbot's built-in messages are sent in nine languages.
• The chat simulator's Reply as tests a flow in any of its languages.
• Publishing waits for any translation that can't be used to be fixed. Out-of-date translations and over-long labels are warnings.
• The Translations workspace (canvas More menu) lists every message once per language. Translate a message used in many places once, translate everything with AI on paid plans, and download or upload a sheet for a translator or reviewer. See The Translations workspace.
• The AI builder writes built-in translations when asked for a bot in several languages, and keeps a node's existing translations when it edits it.
• Messaging and Integration nodes have translations too, sent in the conversation's language. See Translating your messages.

Automations

• Messages in several languages. Automations have a Languages settings tab, the Translations workspace and Translate with AI. A Messaging node's SMS, and the messages an Integration node sends on WhatsApp, Telegram, Twilio, Infobip, Gmail, Outlook and SendGrid, go in the language saved on each recipient's contact, or a language you choose, and in the original when there is no translation. Republish to apply. See Messages in several languages.
• A WhatsApp template can go out in each language Meta has approved it in, and falls back to its own language when there is no approved variant.
• The Messaging node shows how many SMS parts a message is sent as, and which characters make it longer. Send SMS in plain letters spells accented letters plainly.
• A Loop over a long list no longer stops when its run runs out of time. After about 3 minutes it hands the rest of the list to a fresh run, which picks up at the next item. Each of those runs counts as a run. See Loop.
• A loop that stops before the end of its list, at Max iterations or at the run's time limit, now says so: the run shows as partial, with how many items were not attempted.
• A run longer than about 30 seconds records its result when it finishes. It used to be marked Timeout some minutes later, however it had gone.

USSD

• A dynamic list menu offers n: Next Page only when there is a next page and p: Previous only when there is a previous one, takes N and P too, and shows the same page again for a choice it doesn't have, such as 0. Republish to apply. See Dynamic lists.
• Menus in several languages. USSD projects have a Languages settings tab, and each Menu node a Translations section: its message, option labels and navigation labels are shown in the caller's language, and the numbers callers press never change. See Menus in several languages.
• Language menu makes a menu of the languages a project serves, each in its own language. A caller's choice is used from the next screen on and saved on their contact, so their next session starts in it.
• Publishing checks each language's screens: a translation that changes a menu's numbered options can't be published, and one that makes a screen too long is a warning. Send SMS in plain letters also covers USSD screens.
• SMS, integration messages, AI answers and the error screen follow the caller's language.

Voice

• Calls in several languages. Voice projects have a Languages settings tab, and every voice node a Translations section: each prompt is spoken in the caller's language, with a voice for that language. See Calls in several languages.
• Language menu on the IVR Menu node lets callers pick a language on the keypad. The choice is saved on their contact, so their next call starts in it.
• Gather Input listens in the caller's language, and AI Voice Agents speak and listen in it.
• Languages without a text-to-speech voice, such as Kinyarwanda, are spoken in the original for now; publishing says which.

Plans and pricing

• The 7-day Pro trial replaces the free plan (5 October). A new workspace starts on it when you sign up, with no card, and gets everything in Pro, including Inbox translation, live collaboration, voice note transcription and the newer AI builder models. The trial has 10 projects, 5 team members, 50,000 data store records, 30 voice minutes in the simulator and 200 AI credits for the AI builder. See The 7-day Pro trial.
• During the trial you build and test in the simulator, as on the free plan: Publish asks you to upgrade, and drafts take no real traffic. When the 7 days end, the workspace is read-only until you choose a plan. Nothing is deleted.
• Admins get an email when 2 days of the trial are left and another when it ends, and a notice in the app counts down the last 3 days. Each email address gets one trial, and Pro and Business packages no longer start with a card trial.
• When a trial ends without a plan, projects a workspace published on the old free plan stop taking traffic until a plan is chosen: chatbots stop replying, USSD and phone callers hear that the service is unavailable, and automations stop. A trigger's 402 says the trial ended (paused.reason is trial_ended) rather than that credits are used up. See The 7-day Pro trial.
• An automation run includes its first minute, and each minute it starts after that uses 1 credit. A run used to include its first 3 minutes, with 2 credits a minute after that. Most runs finish in seconds and cost 1 credit as before. See Billing and usage.
• Every package now includes more as its price goes up: more data store records, voice minutes, projects and team members. Monthly packages from $45 also include more credits for the same price, and no monthly package includes less than before.
• Pro and Business no longer cap automation runs and API calls at 100 or 150 a month: each one uses a credit. The free plan's cap rises from 3 to 200 a month.
• AI on Buni.ai's key uses far fewer credits: 1 per 800 tokens read and per 250 written, so a short answer is 2 credits.
• An annual package is twelve months of its monthly package at 10% off, with its credits as one pool for the year.
• The pricing page and the upgrade dialog show what each package includes, and the dialog marks the package you are on. See Billing and usage.
• On the free plan, drafts no longer take real traffic. A USSD short code or phone number can't point at Draft, a webhook trigger's Test URL answers 402, and a draft's schedules and other triggers don't run. Test in the simulators and the automation run panel. See Billing and usage.
• Runs started from a trigger URL now stop at the free plan's monthly cap and when credits run out, like every other run.
• Usage billing: on Pro and Business, everything can keep running past your credits, billed monthly at your package's own rate, and voice past your minutes at $0.02 a minute. Without it, and on the free plan, chatbots, USSD, automations and API calls pause until your credits renew, with a notice in the app at 80% and when they run out. See When your credits run out.

September 2026Copy Anchor Link

Inbox

• Filter conversations by Assigned to me and by status (including resolved), with filters kept in the URL and faster, paginated loading of long lists.
• Agents can draft replies grounded in the project's knowledge base, and reply to customers who write in another language.
• The bot stops answering a customer once a human agent has taken the conversation.
• Opening a conversation is faster, jumps to the latest message, and shows new messages as they arrive.
• Template messages show their buttons, and a customer's button tap is labelled as a tap.
• Agents get alerts when the bot escalates a conversation, not only on supervisor assignment. See Inbox.
• Every Live Chat node setting now works. Include conversation history off shows agents only what follows the transfer. Priority level decides which waiting chat goes first. When the wait is too long keeps the chat waiting, hands it back to the bot with a message, or asks the customer to leave a message or a callback number and opens a case. See Live Chat.
• Waiting chats go to an agent as soon as one sets themselves Available, not only when someone frees up, and they're picked with the node's own assignment strategy.

WhatsApp

• Buni.ai-owned service templates are designated automatically, and replies that fall outside the 24-hour window are queued instead of dropped.
• WhatsApp assignment alerts use a template the project owner picks.
• Template previews show the header and footer, and templates with variables submit their example values to Meta. See WhatsApp templates.

AI and knowledge base

• Each project can set a time zone and opening hours; AI nodes know today's date and whether you are open, and can hand off out of hours.
• Knowledge base retrieval returns more of your documents, and topK now controls how much is retrieved.
• GPT-5 family models work in AI nodes.

Building

• Buni plans larger changes as a checklist and builds them task by task; you can send it messages while a build is running, and its clarifying questions sit above the message box. See AI assistant.
• Generated flows are replayed and checked before they are handed over.
• An opt-in setting lets Buni use messages your bot did not understand to suggest improvements.
• API and Integration nodes capture the response on the failure path too.
• A Loop can be paced to stay within a provider's rate limit. See Loop.
• New sign-up flow, project creation and product tour.

August 2026Copy Anchor Link

Voice (IVR)

• IVR projects arrive: build call flows with nodes such as Incoming Call, Play Message, Menu, Collect Input, Record, Transfer, Queue and End Call, and connect your voice carrier. See Voice (IVR).
• AI Voice Agent node with a greeting, handoff message and the knowledge base documents it answers from.
• Outbound calls, call recording (including whole-call recording) with playback, provider voices, and call usage in billing.
• Agents take calls in the browser with a softphone and pick a transfer target from a list.
• Collect Payment node for mobile money and hosted card links. See Collect Payment.

Automation

• Multi-trigger automations: add several triggers to one workflow, including Webhook, Schedule, Manual, Form and app triggers (early access). See Automation triggers.
• Clearer run traces and loop handling in automation activity.

Knowledge base

• Better retrieval quality, a card layout with a preview of each document's chunks, and fixes for uploading and replacing files. See Knowledge base.
• AI nodes send the customer's actual message when a prompt uses {{ }} variables.

WhatsApp

• Create WhatsApp templates in Buni.ai or import existing ones, with their approval status.

Buni (AI assistant)

• Buni proposes a plan you approve before it changes your flow, and you can undo its changes.
• More reliable connection to the assistant, with visible progress while it thinks.

Workspace

• Per-section access permissions, granted from the users page. See Users and roles.
• Privacy notice at sign-up and data processing agreement acceptance.
• Unsubscribe link in the weekly digest email. See Weekly digest.
• The app tells you when you are running an older version and offers a reload.
• Credential fields use a picker that hides saved secrets.

July 2026Copy Anchor Link

• Forms: collect structured answers inside a conversation with the Form node. See Form.
• Approval and durable Wait nodes pause an automation until someone decides or the time passes. See Approval.
• Bot replies stream into the web chat widget as they are generated.
• The AI Agent node gets a wider set of tools, with tooltips.
• WhatsApp shows a typing indicator while the bot works.
• Group nodes and add sticky notes on the canvas.
• Buni can write documentation for a flow. See Documentation tab.
• Real-time collaboration is more stable: presence, avatars and node locking.
• Instagram connects through Instagram's own login again.

May 2026Copy Anchor Link

• Plan limits for projects and other resources are enforced per organization. See Billing and usage.
• The API Access settings tab is reorganised into keys, endpoints and advanced settings. See Project API settings.
• Improved connections for integrations.
• "Embed" is now called chat widget throughout the app.

April 2026Copy Anchor Link

• Buni can ask you clarifying questions before it builds.
• API and Integration nodes have a failure path, and the API node can capture the response. See Error handling.

March 2026Copy Anchor Link

• Public API: call chatbots, flows and automations from your own systems with project API tokens, sync or async, with callbacks, scheduling and quotas. See Developers.
• Automation projects, with a workflow builder and activity view.
• Managed webhook subscriptions for Stripe, Shopify and GitHub, and polling triggers.
• The app works on mobile screens.
• Improvements to the Contact node, the Function node editor (snippets), integration connections and data tables.
• WhatsApp connections use the phone number ID.

February 2026Copy Anchor Link

• The chat widget opens from a launcher button, shows an unread count, and has WordPress position presets; embed codes are shown in a code editor. See Web chat widget.
• Live chat improvements for agents: clearer message authors and session handling.
• Collaboration fixes, and project access managed from the project.

January 2026Copy Anchor Link

• New web chat widget with theming, including a primary colour and automatic contrast for dark backgrounds.
• Feedback form and automatic session end after inactivity in the chat widget.
• Knowledge base reads PDF files reliably.
• Tighter security for embedded chat: messages are only exchanged with the page's own domain.