What we do
Tools
Industries
Department
How we workLet's talk →
Home/Salesforce/Salesforce Flow Builder
Salesforce

Salesforce Flow Builder: Picking the Right Flow and Building It Safely

Flow Builder is where all new Salesforce automation is built now. You arrange elements on a canvas to read records, make decisions, change data or show a screen, and choose what starts the flow. Below: how to open it, which flow type fits the job, a record-triggered flow built step by step, and the mistakes that only show up once real data hits it.

Short answer

Open Flow Builder from Setup: type Flows in Quick Find, open it, and click New Flow.

Setup Process Automation Flows New Flow

Pick a type from what starts it: a record change, a user on a screen, a schedule, a platform event, or another flow or Apex calling it.

Nothing runs until you activate it. Use Debug first, then Activate. Changing an active flow means saving a new version, and only one version runs at a time.

Which flow type fits the job

You want to Flow type Watch for
Change fields on the record being saved Record-triggered, optimised for Fast Field Updates Runs before the save, so it's quick, but it can only update that same record.
Create or update related records, send email, call an action Record-triggered, optimised for Actions and Related Records Runs after the save. This is where most old Process Builder logic ends up.
Do something days after a change, such as a renewal reminder A scheduled path on a record-triggered flow This replaces time-dependent workflow actions. Base the timing on a date field, not on when the record was saved.
Guide a user through a form or a multi-step task Screen flow Launched from a button, a Lightning page or a utility bar. It runs as the user, with their permissions, unless you set it otherwise.
Check a batch of records every night or week Schedule-triggered flow Filter the records in the start element. Sweeping a whole object every night can hit limits as the org grows.
Reuse logic from several places Autolaunched flow (no trigger), called as a subflow or from Apex Keep its inputs and outputs few and clearly named so other flows can call it safely.

A record-triggered flow, step by step

Example job: when an opportunity is marked Closed Won, create a kickoff task for the account owner.

  1. 1

    Start a record-triggered flow

    New Flow Record-Triggered Flow

    Choose Opportunity as the object and A record is created or updated as the trigger.

  2. 2

    Set entry conditions

    Stage equals Closed Won. Then choose to run the flow only when a record is updated to meet the condition requirements.

    Watch for: skip that last setting and the flow runs on every later edit to a won deal, creating a new task each time.

  3. 3

    Optimise for Actions and Related Records

    Creating a task is a related record, so this flow runs after the save.

  4. 4

    Add a Create Records element

    Create a Task with the subject, a due date a few days out, WhatId set to the opportunity, and the owner set to the account owner from $Record. Need the account's fields? Reach them through $Record rather than adding a Get Records element.

  5. 5

    Add a fault path

    On the Create Records element, add a fault path that sends an email or posts a message with the error. Without one, the user saving the record sees a generic error and an admin gets an email that's easy to miss.

  6. 6

    Debug, then activate

    Run Debug against a test opportunity, check the task appears where you expect, then Activate. Build and test in a sandbox first if the object has other automation on it.

Flows that work in testing and fail on real data

Get Records or Update Records inside a loop

How you'll know: The flow works on one record and fails when a data import or list edit saves 200 at once.

Fix: Salesforce caps queries and data changes per transaction. Collect changes in a collection variable inside the loop and run a single Update Records after it.

An old rule and a new flow on the same object

How you'll know: Fields change twice, or emails go out twice, after a flow goes live.

Fix: List every Workflow Rule, Process Builder process, flow and trigger on the object before adding more. Each field should have one owner.

Hard-coded IDs

How you'll know: A flow references a record type, queue or user by its ID and breaks after a deploy from sandbox.

Fix: Look the record up by its developer name with Get Records, or store the value in custom metadata.

No fault paths

How you'll know: Users report a vague error on save, and nobody can tell which flow caused it.

Fix: Add fault paths to every element that touches data or calls out, and send the error somewhere a person reads.

Workflow Rules and Process Builder after end of support

Salesforce ended support for Workflow Rules and Process Builder on December 31, 2025. Existing rules and processes still run, but they get no bug fixes and no help from Salesforce support, so any new automation belongs in Flow.

The Migrate to Flow tool in Setup converts a Workflow Rule or Process Builder process into a draft flow, carrying over its criteria and actions. Not every action converts fully, and some need finishing by hand in Flow Builder. Test each converted flow in a sandbox, activate it, and deactivate the original in the same change, so the two never run side by side.

Process Builder processes often called each other or ran in an order nobody wrote down. Before converting, list what each one does to which fields. That list is usually where the bugs hiding in an old org come out.

Where Flow Builder needs help from code

Flow can call an outside REST API with its HTTP Callout action, set up against a named credential. That suits a simple request to a well-behaved API. Once the job needs retries, paging, signed requests or reshaping a large response, the cleaner design is an Apex class exposed to Flow as an invocable action, so admins keep editing the flow and the hard part stays in tested code.

Some systems the flow needs to reach have no API at all: an older vendor portal, a carrier's site, an internal tool. For those, n-frames builds browser automation that does the step the way a person would and writes the result back to Salesforce, where the flow picks it up. Integrations going the other way, with outside systems writing into Salesforce, are covered under the Salesforce REST API, and pipeline automation on deals under Salesforce opportunities.

Questions people ask

What's the difference between Workflow Rules, Process Builder, and Flow?

They're three generations of Salesforce automation. Workflow Rules handled field updates, email alerts and outbound messages on one object. Process Builder added related records and more actions, but got slow and hard to follow at scale. Flow replaces both, and adds screens, loops, subflows, schedules and callouts.

Are Workflow Rules and Process Builder being retired?

Support for both ended on December 31, 2025. They keep running in orgs that have them, but Salesforce no longer fixes or supports them. Use the Migrate to Flow tool to convert them, and test each one before switching the old version off.

Can a Salesforce flow call an external API?

Yes. The HTTP Callout action calls a REST endpoint through a named credential. For error handling, retries or complex responses, an Apex invocable action that the flow calls is more reliable.

What is a validation rule in Salesforce?

A formula that blocks a save when data breaks a rule you set, for example no Closed Won without an amount. Validation rules stop bad data at the door. Flows act on data once it's been saved, so the two work together rather than overlapping.

What's the difference between a screen flow and a record-triggered flow?

A screen flow has a person in it: someone launches it and clicks through its screens. A record-triggered flow has nobody watching: it runs in the background when a record is created, updated or deleted.

When should I use Apex instead of Flow Builder?

When the logic loops over large record sets, needs proper error handling around an outside call, or is too tangled to follow on a canvas. A common split is Flow for the steps an admin will change and an Apex action for the one step that needs code. The Apex page covers that side.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.