Salesforce Flow Builder Decision Guide

Start with the moment the automation must run

Before opening Flow Builder, identify what starts the process. A record change, a user-guided interaction, a schedule, a platform event, or a background request each points toward a different flow type.

Write the trigger and expected outcome in one sentence. This prevents a solution from becoming more complex simply because several Flow features are available.

• Use a record-triggered flow for work caused by a record change.
• Use a screen flow when a person must review or provide information.
• Use a scheduled flow for time-based processing across eligible records.
• Use an autolaunched flow for reusable background logic invoked by another process.

Choose before-save or after-save deliberately

A before-save record-triggered flow is designed for efficient updates to the triggering record. An after-save flow is appropriate when the process must create related records, send notifications, invoke actions, or work with records after the original save.

The exam skill is not memorising labels; it is matching the required operation to the transaction timing.

Control entry and repeat execution

Define precise entry criteria and decide whether the flow should run whenever a record meets the conditions or only when it changes into that state. Loose conditions can create repeated work and confusing side effects.

When updating related data, consider whether that update can trigger the original automation again. Use changed-value checks and clear responsibility boundaries to reduce recursion.

Design for collections and failure

Salesforce may process many records together. Keep queries, updates, and actions outside item-by-item loops where possible, and collect changes before performing data operations.

Add fault paths for operations that can fail. A useful failure experience records safe diagnostic context and gives an administrator or user a meaningful next step without exposing sensitive data.

Practise the decision, not the canvas

For each scenario, state the trigger, timing, records affected, interaction required, volume, and failure behavior before choosing a Flow type. Then explain why the nearest alternative is less suitable.

Use current Salesforce documentation and a safe practice org alongside original scenarios because platform capabilities evolve.