Flow Builder Structure

Published July 25, 2026

Flow structure is the mental model for how an experience works from the moment someone opens a public link to the moment they reach an outcome. A QuizFlow Labs flow can be a simple linear questionnaire, a branching decision flow, a smart link-in-bio funnel, or an AI-assisted experience with Agent Steps and external API calls.

The builder is easiest to understand as layers: entry, routing, question blocks, automation, decision logic, completion, presentation, and publishing.

Builder layers

Use these layers when you decide where a setting or behavior belongs.

Entry layer

Every public quiz starts at a hosted link, usually /q/{slug}.

• Introduction & Flow Details defines the flow title, slug, introductory message, social links, header visibility, and header image settings. See Introduction & Flow Details.
• Flow introduction gives visitors a lightweight introduction before they start.
• Bio Funnel Builder can replace a basic intro with a full pre-start landing page. It can show sections, containers, flexible Forms, cards, contact details, and smart buttons before the guided flow begins. See Bio Funnel Builder.

Use the Flow introduction when visitors only need a short introduction. Use Bio Funnel when the page needs to qualify, explain, sell, route, or capture before the first question.

Routing layer

Routing controls where the participant enters or moves next. This is where QuizFlow Labs becomes more than a static form.

Use Intent Paths when one quiz supports multiple visitor goals but still shares one builder, one submission flow, and one analytics surface.

Flow body

The quiz body is built from ordered blocks. Participants move through those blocks unless Jump Logic, intent routing, cards, checkout routing, an Agent Step, or another configured destination sends them somewhere else.

For the full reference, see Question Blocks and the individual block guides.

Automation layer

Automation steps run inside the quiz flow and can change what happens next.

• API Step sends quiz data to an external service, captures response values, stores variables, and can define a failure fallback. See API Step.
• Agent Step uses AI instructions to generate responses, set structured variables, surface cards, or route participants before lead capture or an outcome. See Agent Step.

Use deterministic blocks and Jump Logic when the rules are known in advance. Use Agent Steps when the quiz needs flexible interpretation, generated recommendations, or chatbot-style guidance based on participant context.

Decision layer

Decision logic controls how the quiz adapts.

See Logic & Branching, Response Tags, and Scoring Logic for the detailed setup.

Outcome layer

Completion is the final participant-facing result.

• Write the outcome title and message.
• Insert variables when the result should include names, scores, API values, or Agent outputs.
• Choose whether participants see the total score.
• Choose whether participants can review submitted answers with Display responses.
• Add Conditional Outcomes when different scores, saved values, or intent paths should produce different results.
• Add completion CTA goals when the next action should be tracked.

Use Outcomes when you are ready to define what the participant sees after the quiz.

Shared closing sequences

Intent-specific questions do not need separate copies of every closing step. Several intents can converge on one shared sequence:

1. Reusable Content Page
2. Separate consent or acknowledgement fields
3. Optional soft-gated Lead Capture
4. Outcome

Use an intent end route to send each path to the first shared step. The completion response summary includes only questions encountered on the participant's actual route.

Presentation and publish layers

After the flow is built, configure how it appears and where it will be shared.

Step-by-step setup

1. Start in Introduction & Flow Details to name the flow, set its slug, and configure the public entry page.
2. Add a Bio Funnel only if visitors need a richer pre-start page before the first question.
3. Create Intent Paths if one quiz should support multiple entry goals or start points.
4. Build the quiz body with question blocks, interactive blocks, content steps, lead capture, or advanced steps.
5. Add API Steps or Agent Steps when external data, AI output, variables, or dynamic routing are needed.
6. Configure Jump Logic, response tags, variables, scoring, or intent end routes where the flow needs decisions.
7. Set the default outcome message, result display, score display, actions, and any Conditional Outcomes.
8. Configure Appearance, then publish or update the quiz from Finish & Publish.
9. Copy Installation Code from Finish & Publish when you are ready to embed the saved presentation on your site.
10. Test the public /q/{slug} link and any intent, Bio Funnel, embed, or chatbot entry points you plan to share.

Tips

• Keep the first version simple. Build the main path first, then add branching, intents, API calls, and Agent Steps.
• Use Bio Funnel for pre-start context and routing. Use question blocks for participant input.
• Use deterministic logic for rules that must behave the same way every time.
• Use Agent Steps when the quiz needs interpretation, generated recommendations, or flexible guidance.
• Test every route that skips ahead, starts at an intent, launches another quiz, or depends on a variable.
• Disable Display responses when participants should see the result but not a full answer review.
• Publish and test after structural changes, especially when links, intents, or advanced steps changed.