Your first Salesforce flow will work perfectly. ⚡
Last updated November 2026
Your tenth will quietly fire on the wrong records, and your twentieth will make nobody want to touch the object at all. Here is how to build Salesforce flows the right way from the start, with one complete example and the habits that keep automation boring in the best way.
- Salesforce flows are the main tool for automation in Salesforce, built in Flow Builder without code
- There are five flow types, and record triggered flows are the ones admins build most
- Use a before save flow to update the same record and an after save flow for related records, tasks and emails
- Entry conditions, fault paths and clear names prevent most flow problems
- Workflow Rules and Process Builder are no longer supported, and the Migrate to Flow tool helps move them
What are Salesforce flows?
Salesforce flows are automations built in Flow Builder that run when a record changes, on a schedule, from a screen a user fills in or when a platform event arrives. They can create, update and delete records, send emails and notifications, call Apex and connect to other systems, all with clicks instead of code.
Flow is the automation tool Salesforce invests in. Workflow Rules and Process Builder reached end of support at the end of 2025, and the Migrate to Flow tool in Setup helps convert what is left.
Which flow type should you use?
| Flow type | Starts when | Typical use |
|---|---|---|
| Record triggered | A record is created, updated or deleted | Update fields, create related records, send alerts |
| Screen | A user opens it from a page, button or action | Guided forms, wizards, data entry |
| Schedule triggered | At a set time and frequency | Nightly cleanup, reminders, renewals |
| Autolaunched | Another flow, Apex, a button or the API calls it | Reusable logic called from many places |
| Platform event triggered | A platform event message arrives | Reacting to events from integrations |
How do you build a record triggered flow step by step?
Here is a complete example to build in a sandbox. When an opportunity moves to Closed Won, the flow creates a follow up task for the owner to start onboarding.
More flows than anyone can explain?
Book a flow review. We map your automation, find what overlaps and fix what breaks.
Before save or after save?
| Before save (Fast Field Updates) | After save (Actions and Related Records) | |
|---|---|---|
| Use it to | Update fields on the record that triggered the flow | Create or update related records, send emails, call actions |
| Speed | Much faster, because no extra save is needed | Slower, because it runs after the record is saved |
| Example | Set a Region field from the Billing Country | Create an onboarding task when an opportunity is won |
A simple rule works for most admins. If the flow changes only the record that triggered it, use before save. If it touches anything else, use after save.
What habits keep flows from breaking?
Build and test every flow in a sandbox first. Our guide to Salesforce sandbox types explains which one fits.
How do you debug a flow that misbehaves?
- Run Debug in Flow Builder. Choose a real test record and watch each element and its values
- Read the flow error email. It names the element that failed and the record that triggered it
- Check Paused and Failed Flow Interviews in Setup. Failed runs stay there with details
- Open Flow Trigger Explorer. See every flow on the object and the order they run in
- Use debug logs for complex cases. Set a trace flag on the user and check the workflow and Apex categories
If your flows need a second pair of eyes, our Salesforce automation consulting team and the Salesforce health check are good places to start. You can also test us on one broken flow with our 10 free hours trial.
Common questions
Should I use Flow or Apex?
Use Flow for most automation an admin needs to maintain, such as field updates, related records, notifications and guided screens. Use Apex for complex logic, heavy data processing or integrations that Flow cannot handle cleanly. Many orgs combine both, calling small Apex actions from flows.
How many flows should one object have?
There is no hard limit, but fewer flows per object and trigger are easier to understand and debug. Group related logic into one flow where it stays readable, set the trigger order where several flows run, and use Flow Trigger Explorer to see everything on the object.
How do I test a Salesforce flow?
Build it in a sandbox, run Debug with real test records, then test in bulk by loading around 200 records. Check that fault paths send errors to your team. For critical flows, add Flow tests in Flow Builder so you can rerun them after every change.
What happened to Workflow Rules and Process Builder?
Salesforce ended support for Workflow Rules and Process Builder at the end of 2025. Existing automations may still run, but they get no fixes. Use the Migrate to Flow tool in Setup to convert them, then test each new flow in a sandbox before you activate it.
Good automation is invisible, and people only notice it when it is missing.
Book a flow review
We map your flows, find what overlaps and fix what breaks, before users notice.
If your org already has more flows than anyone can explain, book a flow review with us, and follow TrueSolv on LinkedIn for more admin guides.
Tell us about your automation
Leave your details and a few words about your flows. We will set up a call to map what runs, what overlaps and what breaks.