Work that runs without you in the loop

Routines & automations

Playable below — no signup

Scheduled routines for the recurring questions, full workflows for the recurring work — and three ways to build either. Describe it in a sentence, drag it together on the canvas, or let Bee Flow point at the work it can already see you repeating. The real builder is open further down this page.

Try the builder

Live demo

The actual builder, in your browser

Open a workflow, click a node, change a prompt, drag a step. This is the same interface the product ships — it is running on sample data instead of your mailbox.

Sample data only. The demo has no network access, so nothing you do here is saved, sent or billed — reload and it is back as it was.

Three ways in

You do not have to start with a blank canvas

Most automation tools give you one way to build and assume you already know what you want. These are the three real entry points, in the order people actually use them.

Describe it, and watch it get built

Say what you want in a sentence. The builder assembles the flow on the canvas step by step, explaining what it added and why, and leaves you something you can read and correct. It is a first draft you own, not a black box you configure — the same builder exists for internal apps, web apps and this website.

Every Monday at 07:30, summarise what changed with our competitors and mail it to the team

Or build it by hand

Twenty-four step types with real control flow — conditions, switches, loops, parallel branches, filters, deduplication, waits, HTTP calls and code. Drag to connect. It refuses to let you build a cycle, which is the failure you would otherwise find at three in the morning.

search → loop → extract → aggregate → condition → approval → notify

Or let it point at what you keep repeating

Press "find repeating work" and Bee Flow reads ninety days of your tool activity, looks read-only at your connected apps, and proposes automations for the patterns it can actually see — each labelled with how often it observed one. Suggestions grounded in your activity are separated from general ideas, so you can tell which is which. It runs when you ask it to; nothing scans in the background.

gmail_search ×45 in the last 30 days · weekly · grounded in your activity

What you just used

The parts that make it survivable in production

27 step types, not just "call the AI"

Conditions, switches, loops, parallel branches, filters, dedupe, aggregation, date maths, waits, HTTP requests and sandboxed code — plus AI steps where a model genuinely helps.

Four ways to start

A schedule, an inbound webhook, a manual run, or one of thirteen events in a connected app — new mail, a changed file, an upcoming meeting.

Approval gates

Pause the run and wait for a person before anything irreversible happens.

Dry runs

See what a workflow would do, step by step, before letting it do it.

Run history

Every run keeps a per-step log, with sensitive values redacted rather than printed.

Already using n8n?

Existing workflows can be imported and converted, so moving over is not a rewrite. Automations also export to a file, which makes them reviewable and portable.

Two shapes of automation

Pick the one that fits the job

A routine, when you want an answer

Every Monday at 07:30: what changed with our competitors?

A scheduled agent run with your instructions, your knowledge and your tools. The result lands as a message you can read, forward or feed into something else.

An automation, when you want work done

On a new file in /Clients: classify it, ask for approval, file it.

A graph of steps with real control flow. It reads and writes in your connected systems, and stops for a human whenever you tell it to.

A Step, when you want to reuse it

Vendor lookup → used by four automations and exposed to chat.

Package a fragment once, publish it, and call it from anywhere — including as a tool your assistants can use in conversation.

FAQ

Before you build one

Can an automation touch production systems?

Only the ones you connect, only with the tools you enable, and only within the permissions of the account you connected. Read-only connectors stay read-only — the AFAS and NMBRS integrations, for example, cannot write back.

What stops a runaway loop?

Loops carry a maximum iteration count, runs have timeouts, code steps execute in an isolated sandbox behind an SSRF guard, and concurrency is bounded per automation. A run that misbehaves fails rather than spreading.

Does the AI see everything in the workflow?

Only what a step passes to it, and that still goes through Privacy Shield on the way out. If a step needs no model, do not use an AI step — most of the 27 step types are ordinary logic.

Is this available on the free tier?

Yes. Automations and scheduled routines are Community features, with no cap on how many you run.

Build the one you keep doing by hand

Most teams start with the report they assemble every Monday morning.