Automation
Work that runs whether or not anyone is chatting.
Start a workflow on a schedule, from a webhook or a form, or when something happens in the apps you use. Call your systems, take payments, wait for a person’s approval, and see every step of every run.
Starts on its own
Schedules, webhooks, forms, and events in fourteen apps and your own data.
Waits for people
Approvals asked by email and in the app, with a timeout you set.
Handles payments
MTN MoMo, M-Pesa, Paystack, Flutterwave and Stripe.
Shows its work
Every run keeps a step-by-step record you can read.
Start
Start from anything that happens.
A workflow can have several triggers, and each one can be paused on its own.
Hourly, daily, weekly, monthly or a cron expression, in your time zone.
An address any system can call. Signed requests are verified.
A hosted form. Every submission starts a run.
Run it from the canvas, or from your own software through the API.
Another workflow fails, and this one deals with it.
A record is created, changed or deleted.
A USSD or chat session starts or ends.
Payments, checkouts, invoices, customers and subscriptions.
Orders, refunds, subscriptions, payments and license keys.
New orders, paid orders, new customers and new products.
Orders placed, updated, trashed or restored.
Pushes, pull requests, issues, comments and releases.
Pushes, merge requests, issues, comments, pipelines and releases.
Pushes and pull requests.
Messages, mentions, reactions, new channels and new members.
Messages, commands, button taps and channel posts.
Rows added or changed.
Records created or changed.
New contacts and new deals.
Issues, comments and projects created, changed or removed.
Items created, changed, moved or deleted, and updates posted.
Do
Everything a real workflow needs.
Call any API
HTTP requests with authentication, retries and a path for when a call fails.
Run JavaScript
Reshape data or add logic in a function step.
Ask an AI agent
An agent that uses your integrations as tools, answers from your documents and returns structured data.
Use 65 integrations
Google Sheets, HubSpot, Zendesk, Jira, Shopify, Stripe and more, each with its own actions.
Send messages
WhatsApp templates, SMS, email and Slack, from any step.
Take payments
MTN MoMo, M-Pesa, Paystack, Flutterwave or Stripe, and wait for the payment to clear.
Wait for approval
Ask a person to approve. They are told by email and in the app, and a timeout decides if nobody does.
Wait
Pause for minutes or days and carry on where it left off.
Loop at a safe pace
Work through a list at a rate your systems can take, and decide what happens when an item fails.
Branch and run in parallel
Route on conditions, filter, and run branches at the same time.
Keep records
Read and write data stores and contacts without running a database.
Answer the caller
Send back your own status, headers and body when another system is waiting for a reply.
Examples
What teams automate.
Every evening, text each patient booked for tomorrow with the time and place of their appointment.
Government
Take the registration fee by M-Pesa when the form is sent, and add each paid registration to finance’s Google Sheet.
Government
When a name is added to the distribution list, send that person a WhatsApp message with their collection point.
NGOs
Post every new referral to the duty team’s Slack channel the moment it is recorded.
NGOs
Read each field report with an AI agent, flag the urgent ones and log them all to a Google Sheet.
NGOs
When an invoice is paid in Stripe, mark the account as paid and send the customer a WhatsApp receipt.
Enterprise
Running it
Built to be trusted with real work.
- Run history
- Every run records what started it, each step’s result and timing, and any error.
- Test and live
- Separate addresses for testing and for production, and a test event you can send from the canvas.
- When things fail
- Retries on the steps that call other systems, a path for failures, and a workflow of its own for anything else.
- Repeated events
- An event a provider sends twice runs once.
- Pause
- Switch any trigger off without unpublishing the workflow.
- Public API
- Start runs now or at a set time, follow each one, and cancel or reschedule the ones still waiting, through a versioned API with scoped tokens, idempotency keys and dry runs.
- Signed callbacks
- When a run finishes, Buni.ai can call your system back, signed with a secret you set so the call can be verified.
- Limits
- Calls into your workspace are rate-limited, and each trigger’s address has its own limit.
- Run it againComing soon
- Re-run a failed run from the step that failed.
Tell us what you need to automate.
We’ll reply with how Buni.ai would run it and what it would take.