The Salesforce Spring ’25 release is here, packed with tons of updates to Flow, Salesforce’s powerful automation tool. These enhancements focus on boosting productivity, streamlining processes, and making automation easier than ever for admins and developers alike. Let’s dive into the top 15 new Flow features.
1. Create Responsive Screens with Automatically Triggered Screen Actions (Beta)
You can now run autolaunched flows automatically in the background when the input values associated with screen actions change. Previously, the only way to trigger a screen action was with the click of a button by using the Action Button component. The output can be displayed on the same screen, so your users can see the results of their actions on the same screen without clicking any buttons.
In Flow Builder, create an autolaunched flow that retrieves data and saves that data in output variables. Activate the autolaunched flow. Then, create a screen flow and add a Screen element. Next, add a screen action and select the autolaunched flow that you created. Configure the screen action, and set input values. After that, add another component to the screen element that uses the output of the autolaunched flow. To use the output from the autolaunched flow, in the screen component’s input, select the autolaunched flow, then Results, and finally the output variable from the autolaunched flow. You can see only the variables that were marked as Available for output. Then, save and run the flow.
For example, suppose you want to automatically show all contacts for a selected account record. Create an autolaunched flow that retrieves all contacts for an account. Activate the autolaunched flow. Then, create a Screen flow and add a screen element to it. Add a Lookup component so that users can select an account record. Add the activated autolaunched flow as a screen action and set the input values. This way, the autolaunched flow runs when the input values for the Lookup component change. Lastly, add a Data Table component, and add the Full Name, Email, and Business Phone columns. The output of the autolaunched flow automatically populates the Data Table when the lookup value changes.
At run time, when your user selects an account, they automatically see all the contacts for that account on the same screen—no button clicks required.
2. View Immediate Feedback from Screen Components with Invalid Values
Now your flow user can see whether an input value in a flow screen component is invalid when the user changes the focus to outside the component. For example, the user enters a value for an email component. The component validates that the input value contains the right domain as soon as your user clicks another screen component. Previously, component validation error messages appeared only when you moved to another screen or finished the flow.
3. Guide Users Through Screen Flows with Built-In Visual Progress Indicators
Visually guide your users through the stages of your screen flows by using the built-in progress indicator—no more writing custom code to create your own. Your users see which stage they’re on and how many stages remain. Configure whether you want to show the progress indicator at the top of the screen or in the footer. Pick from a simple-style or a path-style progress indicator. Path-style progress indicators are supported only at the top of the screen.
Progress indicators use stage variables to determine what stage the user is on. When a screen loads, $Flow.CurrentStage is automatically updated to the stage that’s associated with the screen, and the stage is added to the end of $Flow.ActiveStages if it isn’t an active stage already. Create stage resources and define the stage label, order, and whether the stage is active by default or not. Then, select the stage resource under the Stage field of the Screen element, or assign the stage resources manually by using assignment elements.
Finally, to show a visual progress indicator, open the flow version properties. Then, select Show a progress indicator on screen elements and then select the progress indicator type.
The user sees their progress on the page at run time.
4. Assign Stages to Screen Elements More Efficiently
Now you can assign stages to screen elements right from the screen properties editor instead of using assignment elements to set the $Flow.CurrentStage and $Flow.ActiveStages global variables. When a screen loads, $Flow.CurrentStage is automatically updated to the stage that’s associated with the screen, and the stage is added to the end of $Flow.ActiveStages if it isn’t an active stage already. To show users where they are in the flow and how many stages remain, use the built-in progress indicator or a custom progress indicator.
Create your stage resources. For every stage resource, specify the stage label and order, and select whether the stage is active by default or not. Then, when you’re ready to assign a stage to a screen element, from the Screen properties editor, find and select the stage resource under the Stage field.
When used together with the progress indicator, the user sees the stage that they’re in at run time.
5. Create Flows with a New Streamlined Creation Experience
We reorganized the flow creation window to help you create the automation you need quickly and more efficiently. Flows are separated into four main categories, and you can filter and search to find the automation you need.
To access the new flow creation experience, click New Flow from the Automation Lightning app.
6. Access Flow Versions in Flow Builder
To access different flow versions and see their statuses, click the name of the flow in the Flow Builder navigation header.
7. Troubleshoot Your Flow Configuration with Improvements to the Errors and Warning Pane
You can now dismiss warnings that you don’t want to see again from the Errors and Warnings pane. The pane also includes more actionable messages for all elements, with links that direct you to the source of the error on the Flow Builder canvas. Errors are grouped by element so that you can address them more efficiently.
Create a flow, and then click the Show Error icon.
8. Navigate Collection Filter Flow Child Resources Efficiently
You can now search for and select child resources of the Collection Filter element in the updated resource menu within a flow. Previously, you selected the element of the child resource first, and then you selected the child resource.
Create or open a flow. Then add or edit a Collection Filter element. Click in the Apply Filter Conditions field and value. The clickable breadcrumb path (1) helps you identify where you are and navigate resource groups. Recognize resource types quickly with more intuitive icons. To get helpful information (2) about a resource, hover over the resource’s info icon. To create a resource quickly, click New Resource (3).
9. Undo, Redo, and Save As with Keyboard Shortcuts
Increase your productivity with new keyboard shortcuts for undo, redo, and save as.
Use these shortcuts to undo, redo, or save as:
| Command | Shortcut |
|---|---|
| Undo | Windows: Ctrl+ZmacOS: Cmd+Z |
| Redo | Windows: Ctrl+YmacOS: Cmd+Y |
| Save As | Windows: Shift+Ctrl+SmacOS: Shift+Cmd+S |
In Flow Builder, press Ctrl+/ or Cmd+/ to view keyboard shortcuts.
10. Get Help Building Flows Faster and More Accurately with Einstein (Generally Available)
Get Einstein to use the power of generative AI and automatically build flows for you based on your instructions. Describe what you want to automate, and Einstein takes care of the rest. This feature, which is now generally available, includes some changes since the beta release. Einstein now generates more accurate flows, and it does so faster than before. You can help Einstein get even better by using the prominent feedback buttons to provide feedback on your flows.
Turn on Einstein generative AI in Setup. Next, from Setup, in the Quick Find Box, enter Flow Creation with Einstein, and activate it. Create a flow by using the Automation Lightning app. In the Let Einstein Build your Automation section, click Get Started.
Write instructions from scratch (1), or get started with sample instructions (2).
After your draft flow opens in Flow Builder, check the flow for accuracy and safety. Also, before activating, be sure to debug and test the flow.
To get more accurate results from Einstein, share your feedback in the Einstein panel by clicking thumbs up or thumbs down (1). If the flow doesn’t meet your needs, edit the instructions or start over (2) in a new window.
11. Generate a Detailed Description of a Flow with Einstein
Maintaining a flow can be challenging, especially if you didn’t create it. Without a detailed flow description, it can be tough to figure out what the flow does. Now you can use Einstein to summarize an existing flow or a new one as you create it. The summary describes all the flow steps and includes the input and output variables, the objects that the flow changes, and the subflows that the flow refers to. You can then add the generated summary to the flow description to keep everyone informed.
Turn on Einstein generative AI in Setup. Next, from Setup, in the Quick Find Box, enter Flow Creation with Einstein, and activate it. To summarize a flow, open it in Flow Builder. In the Einstein panel, click Summarize Flow. The Einsten panel is open by default. If you don’t see it, click Einstein 
.
After you generate the summary, you can shorten or lengthen it (1). The standard summary provides a high-level overview and includes the objects that were modified in the flow. The shorter version summarizes the flow in one or two sentences.
You can then add the summary to the flow description (2). If your flow has an existing description, you can update the description. Updating the description replaces the existing description with the flow summary.
12. Send Emails with Attachments in Flow Builder
Enhance your Flow Builder emails by sharing documents or files with your recipients by using Send Email action. To attach a file, provide the ID of a file to the Send Email action. The maximum size of the email created, including attachments, is 35 MB.
In Flow Builder, in the element menu, search for and select Send Email. When you set input values, turn on the Attachment ID field, and then add the ID of the attachment. The ID can be of a Document, Content Version, or Attachment items. If you want to add more attachment IDs, enter them as a comma-delimited list.
13. Enhance Flow Performance by Controlling the Number of Records Retrieved with Get Records
When you work with large datasets, you can hit performance issues or governor limits if you use the Get Records element to retrieve all records. If you set an upper limit to control data retrieval, you improve flow performance and reduce the risk of timeouts or errors. Use the All records, up to a specified limit option to set an upper limit on the number of records to retrieve.
To set a limit on the number of records that the Get Records element retrieves, first add a Get Records element to your flow. Then, under How Many Records to Store, select All Records, up to a specified limit (1). Enter the maximum number of records to store (2). The Get Records element retrieves all the records that meet the criteria up to the specified limit.
14. Design Component Errors for a Better Experience
Your developers can now enhance error handling at run time for your Lightning web component on a flow screen. Previously, the input validation error message from the flow appeared only under the component. Now components that manage their own validation can control how and where errors appear without the risk of showing duplicate errors. Use the @api interface to implement the existing validate() method and the new methods setCustomValidity(externalErrorMessage: string) and reportValidity().
Previously, if the component contained an invalid input, the flow displayed an input validation error message below the component at run time. If the component also contained validation logic that displayed an error message, the flow user saw duplicate error messages. Now you can customize how to display the error messages.
For components that contain validation logic, you can now implement these methods to take control of rendering errors.
validate()setCustomValidity(externalErrorMessage: string)reportValidity()
For existing component validation, you can keep the same logic that’s contained in the validate() method. Like before, the flow calls the validate() method when a flow user navigates to the next screen or finishes the flow. The flow calls the new setCustomValidity(externalErrorMessage: string) method when there are input validation errors. When the setCustomValidity(externalErrorMessage: string) method is called, the component stores the input validation error message from the flow, so it can be displayed later. The flow calls the reportValidity() method when it’s time to render any errors that your component is aware of.
15. Monitor All Failed and Paused Flow Interviews from the Automation Lightning app
The new Monitor tab in the Automation Lightning app is your one-stop shop for finding all your failed and paused flow interviews. The Monitor tab provides valuable data about why a flow interview failed. Debug failed flow interviews and resume paused flow interviews all from the Automation Lightning app. Having the necessary information in one place helps ensure smooth and uninterrupted business operations and improves overall efficiency and productivity.
If you’ve enabled access to the Automation Lightning app, the Monitor tab automatically becomes available. View all the paused and failed flow interviews on the Monitor tab.
To debug a failed flow interview, on the Details page of the failed flow interview, click Open.
To resume a pause flow interview, on the Details page of the paused flow interview, click Resume.
Salesforce’s latest release offers transformative features for admins, developers, and end-users alike. By adopting these updates, you can maximize efficiency, enhance collaboration, and deliver exceptional customer experiences. You can find the release notes here!
