Workflow templates solve "automate the repetitive." Builder Mode goes a step further: it lets you build and evolve processing flows the way you'd write code. This is Loopback's differentiator — the evolving Coding Loop.

From "configuring rules" to "describing goals"

Traditional tools have you fill in conditions, pick actions, and hit save — the rule is static. Builder Mode lets you describe the goal in plain language (e.g. "negative refund feedback → assign to the payments group and draft an apology"), click "Generate draft," and the draft appears in the AI chat on the right, where you iterate:

  • Click "Edit" to change it in natural language (e.g. "count ratings below 3 stars too").
  • Click "Next" to move into the pre-launch review.
  • Once it passes, click "Launch" to make it live.

You and the AI are writing a piece of processing logic together, not filling out a form. This "describe → generate → iterate in chat" loop is where the name Coding Loop comes from.

Two gates before launch

A flow built in Builder executes actions automatically, so there's a review before it goes live:

  1. Dependency check: is a channel you want to notify (e.g. Feishu) not connected? It prompts you to connect it first, drop that step, or switch to a channel that is connected.
  2. Impact replay: actions that will run automatically need your explicit authorization, backed by a replay over the last 30 days — how many items this flow would have matched and how many actions it would have triggered back then, so you can gauge its scope.

Hard safety boundaries

"Can evolve" doesn't mean "left to run unchecked": no fully automated outbound replies (drafted replies must be confirmed by a human), no auto-closing P0, and each flow stays at 1–4 focused rules.

Builder loop by plan

Builder loop concurrency varies by plan: Pro 1 concurrent, Max unlimited, Enterprise unlimited plus a private coding agent. The trial (7-day Max) already lets you experience the full Builder loop. For plan details, see Understanding Plans and Tokens.

Why this is a moat

Before coding agents, "letting a flow iterate itself" meant either an engineering team writing scripts or it simply couldn't be done. The Coding Loop productizes "the flexibility of a homegrown script": flexible, without having to keep an engineering team around. To go deeper, read the blog post Coding Loop: Letting Your Processing Flows Evolve Themselves.