2025 Salesforce Flows: The Complete Guide to Lightning Flows

Walkthrough of how to set up your Salesforce Trailhead account, which will be used for the duration of the course to build your own Salesforce Flows.

An overview of upcoming lectures in the Salesforce Flow course. We'll discuss some of the key items like Salesforce Apps, the Setup Menu, and how to access the Salesforce Flow Builder.

Learn how to get started building a Salesforce Flow. We'll learn about the common Salesforce Flow types and get introduced to the Salesforce Flow Builder canvas.

Deep dive into the Salesforce Flow Builder canvas, with a focus on the Salesforce Lightning Flow screen element. We'll add a Display Text component to our Lightning Screen Flow and output the words "Hello World!".

Explanation of the Salesforce Flow data element called the Create Records. This data element allows us to create Salesforce records, using values from the Salesforce flow. We combine this with our previous Screen Element to create a new contact in Salesforce.

Explanation of the Salesforce Flow data element called the Get Records. This data element allows us to find Salesforce records, and store their field values to use later in the Salesforce flow. It is one of the most commonly used data elements in the Salesforce Flow Builder.

Explanation of the Salesforce Flow data element called the Update Records. This data element allows us to update Salesforce records, using values from the Salesforce flow. We combine this with our Get Records element from the previous video to update a contact record in Salesforce.

In this lecture we summarize the basics of the Lightning Flow Builder, discussing the key Salesforce Flow data elements and Salesforce Flow types we learned about in this section.

Learn about your role as a Salesforce Administrator at Universal Containers, and hear the requirements for our first Salesforce Flow challenge.

We'll build out the custom fields we'll need for the Salesforce Flow solution we're building in Challenge 1.

We continue our prework in this video by converting a lead to make sure our field mapping is functional. This is important because it's going to one of the main triggers for our Salesforce Flow.

In this video we cover an in-depth walkthrough of the Salesforce Record Triggered Flow configuration screen.

Now we'll use an Update Records element inside our Salesforce Flow in order to set the Amount value on the triggering Opportunity Record.

We get our first encounter with the Salesforce Flow Debugger, which is an incredible tool for testing Salesforce Flows before turning them on.

Now that our Salesforce Flow ran through the debugger successfully, we can move on to doing a final test in the shoes of an end-user. Testing directly in the UI is a good step all Salesforce Administrators should take when building flows.

We regroup with a summary of everything we learned about Salesforce Flows in our first challenge.

Understand the business requirements of this Salesforce Flow challenge by reviewing a fictional Help Desk case from a Universal Containers team member.

As a Salesforce Administrator, we'll need to create two new user records and a picklist field in order to build this Salesforce Flow.

In this video we use the "F" principle in our FRAME principles to consider another solution to our Salesforce Flow. This is a skill all good Salesforce Administrators have.

Now we'll configure the start element in our record triggered Salesforce Flow.

We use the "R" principle in the FRAME principle-set to reverse engineer our next step. In this case, we add an Update Records element to our Salesforce Flow canvas because we know we'll have to tackle it at some point.

Now it's time to add a Get Record data element to our Salesforce Flow canvas. We also review how ID values work in Salesforce, as this is crucial for both Salesforce Flow builders and Salesforce Administrators to understand.

Having built out our data element, we continue with the challenge by running the flow through the Salesforce Flow debugger.

Next we'll test our solution in the UI. We'll spend some time discussing best practices as a Salesforce Administrator specifically when it comes to working with Salesforce Flows

We put the finishing touches on our Salesforce Flow by resolving the bug we found. We also discuss how to work with Salesforce Flow versions.

Review some of the key things we learned about Salesforce Flows in this challenge.

We discuss the needs of this challenge scenario and talk about best practices for gathering requirements as a Salesforce professional or Salesforce Administrator

In this video we complete the challenge prework by building a new field on the contact object. This is what you would do as a Salesforce Administrator in the business scenario.

We'll walk through the flow challenge in the UI to ensure we understand the requirements. This is a best practice you'll want to pick up as a Salesforce Flow builder. Then, we'll start working on the Salesforce Flow itself.

As Salesforce Administrators we update the page layouts for faster navigation. We also introduce a useful Salesforce Browser Extension.

We follow the F principle in our FRAME principles and consider an alternative solution to building a Salesforce Flow.

This is a key step that all good Salesforce Administrators do.

We configure the Start Element in our Record Triggered Salesforce Flow.

You can use an assignment element to update records in a before save Salesforce Flow. We do that here.

Following our reverse engineering principle, now we use a Get Records to find the Primary Contact in our Salesforce Flow.

We introduce the Salesforce Flow Decision Element for the first time.

Decisions allow us to implement complex branching logic. In this video we set up the default path of our decision inside our Salesforce Flow.

We learned in the last video that we can sort records with a Get Element to determine which ones we find. In this video, we explore this concept more deeply by using a Report to visualize what the sorting process looks like.

Once again we use an Assignment Element to update records in our Salesforce Flow.

With everything built, it's time to debug our Salesforce Flow and make sure it's working properly.

We successfully tested our Salesforce Flow with the debugger, and now we repeat the process in the Salesforce UI itself. As a Salesforce Administrator this is something I do all the time before sending a Flow to an end user.

We regroup and review many of the things we learned about Salesforce Flows in challenge three.

We learn about the challenge requirements for our Salesforce Screen Flow

We get ready to build our Salesforce Flow by creating record types to use during the challenge

We create a Case path to use with the record type we created for our Salesforce Screen Flow

We learn how to add simple fields to our Salesforce Screen Flow

We map our screen fields to the create element inside our Salesforce Screen Flow

We learn how to leverage the rollback element inside a screen flow and how to make a Salesforce screen flow available to end users through the utility item

We learn how to customize the header, footer, and navigation of a Salesforce Screen Flow

We learn how to use choices inside a Salesforce Screen Flow

Master the picklist choice type in Salesforce Screen Flows

Learn everything about how to make your Salesforce Screen Flow reactive

A deep dive on the Lookup Component functionliaty inside Salesforce Screen Flows

Use the Lookup component to set a field in the create element of our Salesforce Screen Flow

First introduction to fault paths inside Salesforce Flows

Test our Salesforce Flow fault path out for real

Learn the best practices of dynamically querying record types in Salesforce Flows

Activate and test the final version of our Salesforce Screen Flow

Summarize everything we learned about Screen Flows in Lesson 4

We'll provide a concept overview of using loops inside flows, and then we'll begin building a screen flow that will help us apply what we learned.

We've started our screen flow, built a record collection, dragged a loop to the canvas, and created a number variable - now it's time to set up our loop logic!

We built our first loop inside a Salesforce screen flow and now we'll define some logic for the loop to execute after it completes.

With our primer on Salesforce Loops out of the way, we can get back into the role of the Salesforce Administrator at Universal Containers and gather some requirements for our next challenge!

As Salesforce Administrators at Universal Containers, we'll build 3 new fields to support the requirements of this challenge. We'll also make some Salesforce Lightning Page updates and briefly review the challenge requirements.

We start building our Record Triggered Flow in the Salesforce Flow Builder. We configure our start element and then set up our first Get Records element

Continuing with our flow, we drag a loop element to the flow builder canvas and use an assignment element to set up our loop logic.

Previously we configured our loop element and our assignment logic, and now we need to use a record collection variable to store our records and then update them with an update element.

We've configured our Salesforce Flow and now we need to test our flow in Salesforce!

After we've successfully tested our loop flow, we can move on to building a before save record triggered flow that will populate the fields Pedro requested we populate on a new Opportunity. All we need is one assignment element!

We test our before save flow and learn an important lesson about optimizing for fast field updates.

Two out of three Salesforce Flows have been built and now its time for the final flow in the challenge. Here, we using a record triggered flow to update related Opportunity records when an Account changes in Salesforce.

We discuss a best practice that good Certified Salesforce Administrators and Salesforce Flow builders use which is to find the right tool for a job. In this video we cover an alternative solution an explore the philosophy of building solutions on the Salesforce platform.

We recap all we learned about Salesforce Flows in Challenge 5.

We'll introduce a brand new Salesforce Flow type - the Scheduled Triggered Flow!

We'll navigate to the Salesforce Flow builder and begin building our first scheduled trigger flow as part of the challenge primer.

We'll add an update element to our Salesforce Flow with the intention to set the Rating field on lead records at the end of each business day.

We'll activate our Salesforce Flow and then validate that it ran as expected by updating the Salesforce lead records we defined in our entry criteria.

We gather our Salesforce Flow requirements from the VP of Marketing, Naomi, and talk about the reverse engineering design principle.

We begin building our Salesforce Flow and review two options for identify records to work with in the scheduled triggered flow 1) a decision element and 2) a formula field.

We'll review how to use the Email action inside a Salesforce Flow, and build an email template that will reduce the amount of maintenance we have to do in the long term.

We spend 5 minutes covering an essential Salesforce Administrator settings screen which allows admins to configure several important automation settings that affect Salesforce Flows

We begin testing our Salesforce Flow, and discuss best practices around successfully debugging a scheduled triggered flow in Salesforce.

We introduce an advanced fault handling mechanism in our Salesforce Flow by creating a custom Error Log object to hold information about Salesforce Flow errors. Very few Salesforce Administrators use this concept and it will be very useful for you to implement in the future.

We review everything we learned about the Salesforce Flow builder in this challenge.

Introduce challenge seven in the Salesforce Flow Course where we work with Lisa, the Vice President of Sales at Universal Containers.

In this pretend discovery call we gather all the requirements we need to successfully build our Salesforce Flow.

We regroup to discuss what we learned about Lisa's requirements and how we will approach building our Salesforce Flow in this challenge.

We create an Opportunity stage and build email templates to support our Salesforce Flow building later in the challenge. Also, we introduce the Salesforce Inspector Extension for the first time.

We build a custom object that we will use inside our Salesforce Flow to track the impact of our new Flow on the Sales Team.

We begin building our Salesforce Flow by discussing the reverse engineering principle, which leads us to creating our send email action.

We build a Get Records element in our Salesforce Flow to query for the contact once we realize that the Send Email action can't be saved without it.

We build another Get Records element in our Salesforce Flow to query for the oldest contact. We also use the Salesforce Inspector extension to experiment with writing SOQL queries.

We use a Create Records element in our Salesforce Flow to log the time saved by our automation to the Automation Analytics custom object.

We introduce the scheduled path inside a Salesforce Record-Triggered Flow, and built out the several scheduled paths we need for our Salesforce Flow to work.

We debug our Salesforce Flow and experience an error which we work to correct.

We build a decision element in our record triggered flow to handle the scenario where a contact record does not exist or does not have an email address. Using a decision to validate certain data has been found will often occur in Salesforce Flows.

We clone our immediate run path to our 2 days later Scheduled Path inside our Salesforce Flow and the rename the elements so that the flow is easy to understand.

We clone our 2 days later Scheduled Path inside our Salesforce Flow, the rename the elements, and debug the functionality.

We clone the 4 days later path to the 6 days later path in our Salesforce Flow, rename the elements, and debug the functionality.

We clone the 6 days later path to the 8 days later path in our Salesforce Flow, rename the elements, and debug the functionality.

We build our final path in our Salesforce Flow by adding an update element to the Closed Lost path.

In this video we dive deep on the four common test scenarios you'll want to remember when working with Salesforce Flows. We activate our flow and then trigger it by updating an Opportunity to the "Working" stage.

We go step by step through the different actions we expect our Salesforce Flow to perform so that we can confirm everything is working.

With everything working as expected, we take a look at the Automation Analytics records created by our Salesforce Flow, to see how they can help us quantify our impact on the business.

We take a look at how we can add a custom time source to our scheduled paths inside a Salesforce Flow, and use ChatGPT to help build the formula we need.

We review everything we learned about Salesforce Flows in Challenge 7.