Flows
A flow is a sequence of steps that does something useful — send a message, create a task, look up a record, call an outside service. You build it visually, by dragging blocks onto a canvas and connecting them, the way you’d sketch a flowchart on a whiteboard.
Once a flow is saved, an automation can run it whenever a trigger fires.
The flow builder
Section titled “The flow builder”The builder has three parts:
- Blocks panel (left) — a searchable palette of building blocks, grouped by category. Click or drag one to add it.
- Canvas (center) — where your flow takes shape. Blocks run top-to-bottom, left-to-right, connected by lines.
- Side panel (right) — the settings for whichever block you’ve selected. This is where you fill in the details, like the message text or which database to read.
Building a flow
Section titled “Building a flow”- Start from the Start block — it’s already on the canvas and it’s where every run begins.
- Add the blocks you need from the blocks panel.
- Connect them in order, so each block knows what comes next.
- Select each block and fill in its settings in the side panel.
- Save. Your flow is now ready to be linked to an automation.
The blocks you can use
Section titled “The blocks you can use”Flows combine a handful of friendly, reusable blocks:
| Category | Blocks | What they do |
|---|---|---|
| Logic & control | If/Else, Iterator, Template Renderer | Branch on a condition, loop over a list of items, or shape text and data between steps. |
| Tasks | Create Task, Update Task, Read Task | Make a new task, change one, or read its details. |
| Chat | Send Message, Create Channel, Add to Channel | Post a message, spin up a new channel, or add people to one. |
| Databases | Create Entry, List Entries | Add a row to a database, or fetch rows with filters and sorting. |
| AI | Generate Message | Have an AI agent write a message with full context. |
| External | Raw HTTP Request | Call any outside API (GET, POST, PUT, DELETE) with headers, a body, and auth. |
Flows are durable and safe
Section titled “Flows are durable and safe”Flows are stateful and durable: BridgeApp saves a flow’s progress after each step. That means a run remembers where it got to, so a failed step can be retried without re-doing everything before it, and you always get an accurate record of what happened. You don’t have to manage any of this — it’s just how flows behave.