Flow Builder

Published July 23, 2026 • Updated July 26, 2026

Build Flow is where you create the participant-facing journey. A Flow Block can ask a question, display content, trigger an action, capture information, set tags or variables, apply scoring, route participants, call an API, or run an AI Agent Step before an outcome.

Use this page as the Flow Builder hub. The individual block guides cover detailed setup; this page explains how the editor fits together and how to choose the right kind of block.

How Build Flow works

Build Flow is an ordered journey. Participants normally move from one block to the next, but routing controls can send them to a later block, reusable Content Page, lead capture, an intent path, checkout, or outcome.

Editor modes

The Flow Builder supports two editing modes.

Canvas guardrails match builder guardrails: destinations are forward-only, lead capture can be a destination, and publish validation remains authoritative.

Add block gallery

Select Add block to open the block gallery. The gallery is grouped by the job each block performs.

Choose the right block

What blocks can contribute

Not every block does every job, but the Flow Builder can produce several kinds of data and decisions.

Use Response Tags, Variables Library, and Scoring Logic when you need the collected data to power personalization or reporting.

Routing and decisions

Routing turns a simple ordered journey into a decision flow.

• Jump Logic sends participants forward based on answers or conditions. See Logic & Branching.
• Intent paths let one flow support named entry paths and assigned blocks. See Intent Paths.
• Content Pages can act as shared informational or acknowledgement steps before consent, lead capture, or an outcome. See Content Pages.
• Cards and product cards can send participants to later destinations or external next steps.
• API Step failure routing can define what happens when an external request fails.
• Agent Step exits can route participants based on AI interpretation or structured outputs.

Recommended build order

1. Add the main blocks in the order most participants should experience them.
2. Write clear prompts and configure required answers, options, labels, and validation.
3. Add tags, variables, and scoring where the answers should power logic, outcome copy, analytics, or exports.
4. Add Custom Form when several related structured fields belong together, or lead capture when contact details should create a lead.
5. Add Jump Logic, intent path assignments, card destinations, checkout routing, API failure paths, or Agent exits only after the main path works.
6. Use Canvas mode to inspect the flow shape and List mode to refine detailed settings.
7. Preview every branch, intent path, API path, Agent route, and outcome before publishing.

Tips

• Keep each block focused on one decision or one piece of information.
• Use Transition blocks when extra explanation is needed before an important question.
• Use variables consistently if outcome copy, Agent instructions, API calls, or analytics need the same value later.
• Keep Jump Logic forward-only and test rules in priority order.
• Use intent paths for meaningful visitor goals, not tiny audience variations.
• Add API and Agent Steps after the core flow is stable.
• Preview the flow after reordering blocks because destinations, assigned paths, and outcome behavior depend on structure.