Choose the Right Screen Component for Your Flow

Flow screen components let you collect input from or display information to users in screen flows. Choosing the right component ensures a better user experience and helps you get the information you want. Components are organized by use case.

Display Information to Users

Use these components to show information, but not collect user input.

Display Text

Use to provide instructions, explanations, or confirmation messages. The Display Text component supports rich text formatting, including bold, italic, lists, and links.

Example: Display a confirmation message after a user submits a case, such as "Thank you for submitting your case. Your case number is {!CaseNumber}."

Display Image

Use when you want to show images, logos, or visual content that help clarify instructions or enhance the user experience.

Example: Display your company logo at the top of a flow screen or show a diagram that explains a process.

Message

Use to display important notifications, alerts, or status messages. The Message component supports different types, such as informational, warning, error, and success messages.

Example: Display a warning message about required actions, show an error notification when validation fails, or confirm successful completion of a task.

Collect Unformatted Text

Use these components when you need users to enter unstructured text values.

Text

Use for short text entries up to 255 characters, such as names or titles.

Example: Collect a customer's company name or a product title.

Long Text Area

Use for open-ended text entries with no character limit.

Example: Collect detailed feedback about a service experience or a full case description.

Password

Use when you need users to enter sensitive information that should be masked on screen.

Example: Collect a password or PIN for verification purposes.

Collect Formatted Text

Use these components when you need specific text formats, such as a phone number or email address.

Email

Use when you need users to enter email addresses. The component validates that the input is a properly formatted email address.

Example: Collect a customer's email address for follow-up communications.

Phone

Use when you need users to enter phone numbers.

Example: Collect a contact phone number for a lead or customer.

URL

Use when you need users to enter website addresses or URLs.

Example: Collect a customer's company website or a link to documentation.

Collect Numeric Values

Use these components when you need users to enter numbers.

Number

Use for whole or decimal numbers, such as quantities or ages.

Example: Collect the quantity of items to order.

Currency

Use when you need users to enter monetary amounts. The component formats the value as currency.

Example: Collect a budget amount, purchase price, or reimbursement request.

Slider

Use when you want users to select a value from a defined range. Best for ratings, satisfaction scores, or preference levels.

Example: Collect a satisfaction rating from 1 to 10 or a priority level from 0 to 100.

Collect Dates and Times

Use these components when you need users to enter dates or times.

Date

Use when you want users to select a date from a calendar picker.

Example: Collect a preferred appointment date, event date, or deadline.

Time

Use when you want users to select a time without a date.

Example: Show available times for an appointment on a predefined date.

Date/Time

Use when you want users to select both a date and a specific time.

Example: Schedule a meeting or appointment that requires both date and time.

Collect Single-Choice Selections

Use these components when users select just one option from a set of choices.

Picklist

Use when you have many options and want to save screen space with a dropdown.. A picklist is ideal if you have many options.

Example: Have users select a product category, department, or priority level from a list.

Radio Buttons

Use when you have 2–5 options and want all choices visible at once. Radio buttons make it clear that the user can select only one option.

Example: Have users select a preferred contact method (Email, Phone, Text) or choose a service tier (Basic, Standard, Premium).

Collect Multiple-Choice Selections

Use these components when users can select multiple options.

Multi-Select Picklist

Use when users need to select more than one option from a dropdown list.

Example: Have users select multiple product interests, languages spoken, or skills from a list.

Checkbox Group

Use when you have a small to moderate number of options and want all choices visible for multi-selection. Users can select multiple checkboxes.

Example: Have users opt into multiple communication preferences or select applicable features.

Collect True or False Input

Use these components for Boolean choices.

Checkbox

Use when you need a single yes or no or true or false choice, such as accepting terms or opting into something.

Example: Have users agree to terms and conditions, opt into a newsletter, or confirm that they understand a policy.

Toggle

Use when you want a visually prominent representation of an active or inactive state.

Example: Have users enable or disable notifications, activate a feature, or switch between two states.

Collect Record Selections

Use these components so users can select existing records from your Salesforce org.

Lookup

Use when you want users to search for and select existing records. The component provides a type-ahead search interface.

Example: Have users select an account, contact, or custom object record.

Choice Lookup

Use when you want to provide a filtered list of records based on flow logic or when you need more control over which records appear.

Example: Have users select from a filtered list of accounts in a specific region or the contacts assigned to them.

Note Learn more about when to use the Lookup component or the Choice Lookup component in Choose a Lookup Option for a Flow Screen

Data Table

Use to display multiple records in a table so users can select one or more. Best for comparing records or viewing details before selection.

Example: Display a list of open cases with details like case number, subject, and status, so users can select which cases to update.

Kanban

Use when you want to display records in a visual board format with columns representing different stages or statuses. Users can see records organized by stage and track workflow progress.

Example: Display opportunities organized by stage (Prospecting, Qualification, Proposal, Closed Won) or cases organized by status (New, In Progress, Resolved).

Collect Multi-Field or Complex Input

Use these components when input spans multiple related fields or when users need to enter repeating data.

Address

Use when you want users to enter a complete address with street, city, state, postal code, and country fields.

Example: Collect a shipping address or business location.

Name

Use when you want users to enter a person's name with separate fields for salutation, first name, middle name, and last name.

Example: Collect a full name for a new contact or lead.

File Upload

Use when you want users to upload documents, images, or other files.

Example: Have users upload a resume, contract, invoice, or supporting documentation.

Dependent Picklists

Use when the options in one picklist depend on the selection in another.

Example: First, users select a product category, then they select a specific product from that category.

Repeater

Use when users need to enter information about multiple items of the same type. Users can add or remove rows as needed.

Example: Have users add multiple attendees to an event, each with their own name and email fields, or collect information about multiple expense items.