How it works

Something happens. Bizomate does the rest, and writes it down.

A workflow is a trigger and a few steps across the apps you already use. Here is what happens from the first click to the thousandth run.

TRIGGERSTEPS
When an order arrivesTrigger · a call from your website
Look up the customerMicrosoft SQL
Is it over ₹50,000?Condition · yes goes on, no stops here
Tell the finance teamMicrosoft Teams
Add to the orders sheetGoogle Sheets
The three parts

Every workflow is the same three things

1

What starts it

The trigger. One per workflow, and it decides when a run begins.

2

What happens next

The steps. Each does one thing in one app — or checks a condition and takes a path, or asks an AI model to read or write something.

3

What it leaves behind

The run record. Every run, step by step: what each one received, what it did, and how long it took.

What can start a workflow
A call from your website or another system A schedule — every morning at 9:00 An email arriving A form being filled in A new row in a sheet or list
Your first workflow

From an idea to running, in four steps

Most people have their first workflow running in an afternoon, without a developer.

1

Start from a template, or a blank canvas

Templates are grouped by job, not by app, and each shows every step before you use it.

2

Connect your apps

Sign in with Microsoft or Google, or paste a key. Keys are encrypted and never shown again — not even to you.

3

Test it on real data

Run a step and see exactly what it received and what it produced. Nothing is live until you publish.

4

Publish, with a note

Every publish is a version with a note saying what changed. Compare two versions, or go back to an earlier one.

The record

Every run is on the record

What started it, what each step received and did, and how long it took — in words anyone on your team can read, not a log file.

How long runs are kept depends on your plan; Pricing lists it.

Large orders · run #4,812 Today at 10:42 · 1.9 seconds
Succeeded
New order from the websiteWebhook · order NW-20417 · ₹84,500 0.1 s
Look up the customerMicrosoft SQL · Northwind Logistics, account 3312 0.4 s
Is it over ₹50,000?Condition · yes, ₹84,500 0.0 s
Tell the finance teamMicrosoft Teams · posted to Finance ops 0.8 s
Add to the orders sheetGoogle Sheets · row 1,284 of Orders 2026 0.6 s
Failed at step 5 Large orders · run #4,799

Google Sheets could not find the sheet “Orders 2026” — it was renamed on Monday. Choose the sheet again, then run this step again.

Run this step again
When something goes wrong

It stops at the step that failed, and says why

Not an error code: what happened, in plain words, and what to do about it. Fix it, then run that step again from the run itself.

The people who look after the workflow are told, so a failure is never found by accident a week later.

For a team

Safe to hand to the whole team

Roles for every workspace

Admins manage it, Editors build and publish, Viewers read the workflows and their runs — nothing more.

A version for every change

See who published what and when, with their note, and compare any two versions step by step.

Bring what you have, take it with you

Import workflows from other tools’ export files. Export yours on every plan, Free included.

What a run costs

A run is one pass of a workflow, however many steps it has. The order above is one run, not five.

Work it out with the run calculator

Pick the thing you do every week. Start there.

The free plan runs 100 times a month, for as long as you like. No card.

Start free