Introducing Flow Agents: steps that read, decide and write back
Agents are now a step type in every workflow. Give one a goal, the tools it may use and the policy it must follow, and it works the queue for you.
By Clara Novak
Blog
Product news, engineering notes and workflow guides from the team building Flow.
Idempotency is the whole job
Why every step in Flow can run twice without doing anything twice, and the three rules we follow to keep it that way.
How Northbeam closes the books in three days
Northbeam's finance team used to spend nine days on month-end. Here is the set of workflows that took six days out, and what they kept for people.
Build lead routing in an afternoon
A step-by-step recipe for routing inbound leads by territory and fit, booking the first call and telling the rep, all within a few minutes of sign-up.
Every workflow needs an owner
Automation that nobody owns decays quietly. Why we made ownership a required field, and what owners actually do each week.
Replaying a run, step by step
How we record enough of every run to replay it later against a new version of a workflow, without calling a single external API.
Approvals that don't stall the work
Approval steps keep people in charge, but badly designed ones turn a five-minute process into a five-day one. Six patterns that keep them fast.
Writing instructions an agent can follow
Agent policies are just instructions. The ones that work read like a good handover note: specific, ordered, and honest about the edge cases.
What 2,000 workflows taught us about automation
We studied the first 2,000 workflows our customers put into production. The ones that lasted had a few things in common, and complexity wasn't one of them.