Help centre Browse

What a Flow is, and when you need one

This explains what a Flow does in plain terms, so you can tell whether your problem needs one.

flows Last reviewed 2026-08-28 · About 2 minutes
The Flows list in BPA, showing five active flows in a table with status, tags and dates
Build → Flows. Each row is one flow, with whether it is currently active.
The Flow Designer, showing a flow as a left-to-right graph: Start, four stages, and two possible End points
One flow open in the Designer. Stages run left to right from Start, and a flow can branch to more than one ending.

A Flow is a set of steps that runs on its own. Something starts it, usually a form being submitted, and then it does the things you would otherwise have done by hand.

A leave request is the clearest example. Someone submits the form, and the Flow emails their manager, waits for a yes or no, emails the person back with the answer, and records the decision. Nobody had to remember to do any of it.

A quick test If you find yourself saying “and then someone has to remember to…”, that is a Flow.

You do not need a Flow to collect information. A form on its own is fine if you are happy to look at the answers yourself.

Was this helpful? Tell us what was missing and we will fix the article.

All help articles Contact us