Flow Block Types

Published July 25, 2026 • Updated October 19, 2026

Use this page to choose the right block before opening a detailed setup guide. The Flow Blocks builder explains the editor; this page focuses on the block library itself.

Flow Blocks include questions that collect signals, content that explains or builds trust, lead capture and structured forms, and advanced steps that perform actions.

Block categories

Core blocks

Visual lessons with Transition

Use an existing Transition block to show one short instruction and a supporting image before asking for a response. Open Settings → Media → Choose lesson image, select an image from your media library, and write an Image description for people using screen readers. The image appears below the text without cropping in the shared flow renderer. Use a combined image to show several positions; keep essential instructions in the text as well.

For a workout, write “Push-ups · 40 seconds. Keep your body straight. Knees are okay.” and show the movement. The player selects Next when ready to record their attempt. Follow it with a Custom Form asking how it went and an optional rep count. A plank can ask for seconds instead. A Transition can optionally time the activity, but does not verify the exercise; the response is self-reported.

This same pattern works for courses: show a lesson → let the learner try → ask a question or reflection → continue. Use a grounded Agent Step for a short recap when helpful. Moving past a lesson alone does not prove learning or completion. Preview on mobile and have a qualified coach review exercise illustrations before using them with players.

Optional countdown timer

Open a Transition’s Settings → Setup, turn on Countdown timer, and set Duration (seconds) from 1 to 3600. It is off by default. For example, use 40 seconds for a workout set, 120 seconds for reflection, or 300 seconds for independent practice.

Players select Start, Pause, and Reset. Start resumes a paused timer; Reset restores the full duration and waits for Start. At zero, “Time’s up” appears and the player chooses when to continue. The timer does not block Next, advance automatically, or mark a lesson or exercise completed. Use a following question or form for honest reporting.

A running timer uses elapsed wall-clock time, so returning from a background tab or screen lock updates the remaining time correctly. A paused timer stays paused. Browsers may suspend display updates while hidden; this feature does not send a background alarm or keep a device awake. Leaving the Transition, returning to it, refreshing, or reopening starts a fresh timer. It does not store progress or timing history. Changes to the device clock can affect the countdown.

Use the written duration alongside the display. Screen readers announce state changes and the end, rather than every second. Preview on a phone and test Start, Pause, Reset, navigation and returning from another tab before sharing a flow.

Structured form block

Interactive blocks

Lead Capture blocks

Advanced blocks and steps

Choose by job

Related functions

Step-by-step

1. Open Build Flow in any decision flow.
2. Select Add block and choose the category that matches the job you need.
3. Pick the simplest block that can collect the right signal or perform the right action.
4. Fill in prompts, options, validation, tags, variables, scoring, or routing as needed.
5. Add Lead Capture before completion when the flow should create a lead.
6. Preview the flow and confirm the block output is available where you need it.

Tips

• Choose blocks by the signal you need, not by visual preference alone.
• Use Multiple Choice or Dropdown when options are known; use Text Response when the answer needs to be open-ended.
• Use Map / Location to show a destination; use Location Qualifier when the Flow must make a serviceability or territory decision.
• Use Ranking only when order matters. Use Multiple Choice when order does not matter.
• Use Transition blocks to reduce confusion before a complex or high-stakes question.
• Add API and Agent Steps after the main flow is stable.
• Test every block that sets tags, scores, variables, routes, checkout behavior, API values, or Agent outputs.