Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full Wizard entry
How-to guide

Build a custom wizard with a Screen Flow

Build a custom wizard as a Screen Flow in Flow Builder. This gives you Next and Previous navigation, stages, and a progress indicator without code.

By Dipojjal Chakrabarti · Founder & Editor, Salesforce DictionaryLast updated Jun 16, 2026

Build a custom wizard as a Screen Flow in Flow Builder. This gives you Next and Previous navigation, stages, and a progress indicator without code.

  1. Create a Screen Flow

    From Setup, open Flow Builder and create a new flow. Choose Screen Flow as the type so the flow runs as an interactive, user-facing sequence of screens.

  2. Add a screen for each step

    Drag a Screen element onto the canvas for every step in your task. Add screen components such as text inputs, picklist choices, and lookups to collect what that step needs.

  3. Define stages and a progress indicator

    Create stages for the major phases of your process and assign screens to them. Add a progress indicator so users can see the current step and what still remains.

  4. Branch and validate

    Use Decision elements to route users based on earlier answers, and set validation on inputs so problems surface on the screen where they occur, not at the end.

  5. Place the wizard where users work

    Activate the flow, then embed it on a Lightning page, a quick action, or an Experience Cloud site so users can reach it at the moment they need it.

Key options
Screen componentremember

A field or display element on a step, such as a text input, picklist, lookup, or repeater, that collects or shows data.

Stageremember

A major phase of the flow used to power the progress indicator and tell users where they are in the sequence.

Navigation buttonsremember

Built-in Next, Previous, and Finish controls that move users between steps and complete the wizard.

Placement targetremember

Where the flow runs, including a Lightning record page, a quick action, the utility bar, or an Experience Cloud site.

Gotchas
  • Crowding one screen with too many inputs defeats the purpose. Keep each step focused on a single decision or a small set of related fields.
  • Guest users on a public Experience Cloud site need the flow shared for guest access, or external users will not be able to run it.
  • Test every branch as a real user before release. A step that works alone can still strand someone when the path order is wrong.

See the full Wizard entry

Wizard includes the definition, worked example, deep dive, related terms, and a quiz.