Many teams still run flows built before 2026, and most online tutorials show this builder.
Before agents, Gumloop was a drag-and-drop workflow builder, and it is still available under a "Legacy" label. You'll meet it in existing accounts and in older tutorials.
The pieces:
- A workbook is a canvas holding one or more workflows ("flows"), each in its own tab.
- A flow is made of nodes: boxes that each do one job, such as reading a Google Sheet, asking an AI model a question, or sending an email. You drag nodes from the library and connect them with lines that show how data moves.
- Since a 2025 redesign, one connection passes all of a node's outputs to the next node, and you choose inputs inside each node. In text fields, typing
@lists earlier nodes' outputs you can reference. - Subflows: select some nodes and click Make Subflow to move them into their own tab, which can be reused inside other flows. Gumloop suggests splitting flows longer than 10 to 15 nodes.
- Run executes the flow and shows a report of each node's progress; Resume continues from a chosen node instead of starting over; Previous Runs shows history.
The Gumloop Chrome extension (still updated in 2026) records actions you do in your browser and turns them into repeatable automations, useful for websites without an API.
Flows can also be started and inspected through the Gumloop MCP server and API.
For new work, prefer agents with triggers and skills. Keep a flow when a job must run exactly the same fixed steps every time; the word "legacy" signals less future development rather than an announced shutdown date.
Remember
- Workbooks hold flows built from connected nodes; subflows are reusable tabs
- The workflow builder is legacy; new work should use agents
- The Chrome extension records browser actions into automations
Watch out for
- Rebuilding a stable, fixed-step flow as an agent without need; predictable jobs can stay as flows until you have a reason to move.