Flows
Build the process once. Run it everywhere.
Flows is a visual canvas where you chain enrichments, waterfalls, AI steps, and if/else logic into one pipeline your whole team, and your agents, can run.
Build reusable pipelines on a canvas
From empty canvas to a running pipeline: waterfall, branch, AI step, CRM sync.
How it works
From canvas to running pipeline in three steps
1. Drag steps onto the canvas
Enrichments, waterfalls, AI research steps, filters, and branches. Chain them in any order.
2. Test on sample rows
Run a handful of rows first. Every step shows its output and its credit cost before you commit the whole table.
3. Run it anywhere
On a table, on a schedule, from the API, or as a tool your agent calls. Same flow, every surface.
Why a canvas
Logic and cost, visible before you commit
Logic that spreadsheets can't hold
If/else branches, filters, and merges are nodes, not nested formulas. A rep can read the pipeline like a diagram because it is one.
Cost you can see before you spend
Test runs show the per-step credit cost on your sample rows. You know what row 10,000 will cost before you run row one.
Run history
Every run is a record
Debug a pipeline like an engineer
Status, output, duration, and cost per step, logged for every run. Not a spreadsheet archaeology dig.
Run surfaces
One flow, four ways to run it
In a table
Runs down 10,000 rows in place, like a formula that does the whole job.
On a schedule
Refresh your CRM every Monday at 6am without touching it.
From the API
Trigger the flow from your product or your pipeline with one call.
As an agent tool
Expose it over MCP and your agent runs it whenever it needs data.
