Standout Announcements from the Flow Builder Product Roadmap for 2025

On Wednesday 5 March, Alex Edelstein of Salesforce shared a newsletter post on LinkedIn. This post included the roadmap for Flow Builder in 2025. This post in a sense is a bit of a sea-change. While transparency from Salesforce Flow PM’s over the last few years has greatly increased, this post is a big step forward. The reason I say this is because we often have to wait for these kind of updates until something like a Release Readiness Live, or after a big event like Dreamforce or TDX (TDX kicks off on Wednesday 5 March for reference). So, as an avid lover of Flow Builder and a bit of an advocate for the work of the Flow team, I’m very happy to have seen this post go live. So much so, that I decided to draft up this post on the same night the post from Alex went live. This post will be released on Thursday 6 April, a little over 24 hours after the initial post from Alex went live. Hopefully this post will serve as a helpful review and commentary of the roadmap. In this post, I will share what I believe are the standout items covered in the roadmap, and why I think those updates are worth keeping an eye on. I will be sharing links to Alex’s post and another below for you to read at your own leisure. I would encourage you to take the time to read both of the posts I share. It will be worth it.

With that all being said, let’s dive into what I feel are the standout updates from the Flow Builder Roadmap for 2025.

N.B. Quick warning, I will not be talking about any Agentforce specific updates in this post. That isn’t my place currently.

Rich-Text Formatting is Coming For Text Input Components:

Where else could I start? If you’ve talked to me about what I feel is one of (if not) the biggest gap in the capabilities of Screen Flow, it’s the lack of ability to create Rich Text via a text input component. In Alex’s post, it has been announced that this functionality is going to finally arrive for Screen Flows in 2025. According to the announcement, Admins will be able to set the type of text input to Rich Text via a toggle. This will be similar to the toggle that is already available for Text Templates. In my view, this is huge. I am very excited to see this functionality come to Screen Flow sometime over the next 12 months. Alex’s post doesn’t highlight when this will be coming, but my guess is that it will either be released in Summer ’25 as a beta enhancement, or it will arrive in Winter ’26 with a bit of fanfare at Dreamforce. Either way, this update is easily at the top of my list of enhancements to look forward to.

Time Fields Will Be Supported as a New Data Type:

The next update on my list to highlight is the addition of support for Time as a data type in Flow Builder. For a number of years, Salesforce has supported Time as a field type. However, Time has not been a supported data type since Flow Builder’s inception.

Time as a supported data type is due to be made available in the Winter ’26 release. So, look for this to be highlighted at Dreamforce in San Francisco in early October. This update will undoubtedly make a lot of Flownatics very happy indeed.

Send Email Action is Being Overhauled for a Better User Experience:

Next up is something which I think is quite cool. That being an incoming overhaul to the Send Email Action. In the Winter ’25 release, we saw an upgrade to the Send Email action with the inclusion of the ability to add CC and BCC recipients to an email. In Spring ’25, the ability to add attachments to an email came to us. So, clearly the Flow team have been hard at work to make this action more performative, and as a result to meet the demands of sending emails via Flow. Let’s not forget how the limit to how many recipients could be emailed was upped from 5 to 150 recipients (combined across To, CC, and BCC) in Winter ’25 as well.

As you will see from the screenshot provided, once these updates go live, the Send Email Action will be split into four sections:

• Recipients Details.
• Sender Details.
• Email Content.
• Show advanced options.

Like with the Rich Text update, it is not noted when this update will go live. My prediction for this is that there will be a beta release of this feature in Summer ’25 with a GA release in Winter ’26. I do have plans to cover the Send Email Action in more depth in a future post. For now, I’m considering holding off on this until this update is testable in a preview org environment. Nevertheless, this will be a substantial upgrade to the Send Email Action. Time will tell if this overhaul will be beneficial, although I think it will.

Multi-Objects Data Shape:

Another key enhancement in the 2025 roadmap is what is being labelled as Multi-Object Data Shapes. In a nutshell, a Multi-Object Data Shape will be a framework where Admins can configure the retrieval of related records in a Get Records Element. In even simpler terms, say you want to grab an Opportunity and it’s related Account and Contact, you will be able to grab all of these records inside of your Multi-Object Data Shape. This will be a bit more complex for Admins with less Flow experience. However, it will be a significant upgrade that will end up simplifying the work involved in retrieving related records as a whole.

As you will see from the screenshot provided, when configuring your Multi-Object Data Shape, Admins will be able to configure which related object/s form part of the data shape.

At the time of writing, it isn’t clear how this will work. The article from Alex also doesn’t state when this update is coming. My guess is that with a new addition this complex, we may be waiting until Winter ’26 for this to be made available to us. This kind of upgrade is historically the kind of thing Salesforce like to announce at their biggest event of the year. So, this will likely be shown off at Dreamforce.

Further Enhancements to the Transform Element:

One of Salesforce’s (almost) best kept secrets in recent upgrades to Flow Builder is the Transform Element. The Transform Element is a modern answer to data transformation in Flow. One of the most prominent use cases for the element is to use it as a means to create collections without the need to use multiple Assignment Elements. Over the course of 2025, more enhancements to the element are coming. 2025 has already seen the release of the ability to join collections into a single data structure. In Winter ’26, the Transform Element will be upgraded to allow for the use of Custom Functions. At the time of writing, it isn’t documented as to how this will work exactly, look to see more details on this coming out ahead of the Winter ’26 release and Dreamforce.

Flow Approval Processes:

Before I conclude with a suite of honourable mentions, I would like to cover Flow Approval Processes. For a few years now, I have commented in discussions that I believed that Approval Processes would eventually transition to Flow. That very easy to make prediction is coming to pass now with the release of Flow Approval Processes. I didn’t know this was coming until I read through the release notes for Spring ’25 as it is now GA. In those conversations where I predicted that this would happen, I also predicted that the new Approval Process framework would likely use the same (or at least similar) mechanics to Flow Orchestrator. This is also something I guessed correctly, as the new Flow Approval Process model is built on the Flow Orchestrator engine. At the time of writing, I haven’t been successful in building out an Approval Process using the same model. However, it is on my to-do-list. Once I have successfully done this, I will be looking to write a blog post unpacking this new functionality and how it works.

Crucially, it is important to note that Flow Approval Processes DO NOT REQUIRE THE PURCHASE OF FLOW ORCHESTRATION. For transparency, Flow Orchestrator currently operates under a freemium model. In that model you get 600 free Orchestration Runs per year. After the 600 run limit has been used, you will need to purchase Orchestration Runs costed at $1 per Orchestration Run. The point that Flow Approval Processes is free for all editions is great. It gives Admins the opportunity to learn more about Flow Orchestrator as a model. And who knows, maybe it’s a move in the right direction to make Flow Orchestrator free on all plans.

Once again, I do have plans to publish a post here once I have figured out Flow Approval Processes. Hopefully that will be soon.

Other Honourable Mentions:

There are a number of other key updates listed in the 2025 roadmap. If I was to cover each update, the result would be a very long blog post. So, rather than cover all of the updates, I have provided my standout updates included in the roadmap. Because this is my list, there are a number of updates not included in this post. Therefore, I have decided to give a list of honourable mentions.

Here are what I would consider to be honourable mentions in the roadmap:

• New create Flow experience (currently only available in the Automation App).
• A manual date picker for date data types.
• Addition of Formula and Transform modes in input selections.
• Improved search functionality in Flow Builder.
• A new Action Hub to help with the management of Flow Actions.
• Trigger conditions for Screen Actions.
• Customisation options to help enhance the look and feel of Screen Flows.
• Custom Images for choices (similar to conditional formatting in Lightning App Builder).
• More new components for Screen Flows.

As you can see, there are a lot of enhancements coming to Flow Builder in 2025. I’m very excited to get my hands on a number of these for testing when they become available in preview environments. This is going to be another big year for Flow Builder.

Closing Comments:

That concludes this post highlighting what I feel to be the standout items in the Flow 2025 product roadmap. I’m sure you will agree that a number of these updates are fantastic, and in some cases, they have been a long time coming. But I want to hear from you. What are the enhancements listed in the roadmap that you are looking forward to the most? Let me know what you think in the comments below. If you have found this blog helpful or interesting, why not share it with a colleague or your organisation.

Featured Resources for This Post:

Below are two resources that are worth reading alongside this post. The first is the roadmap article on LinkedIn that inspired this post. The second, is a post written by a Product VP at Salesforce highlighting the ten best innovations for Flow Builder in 2024. Both of these posts should provide some additional insight into Salesforce’s view on Flow Builder and plans for it in the coming months.

Top Ten Flow Innovations for 2024:

This LinkedIn article from Vijay Pandiarajan at Salesforce highlights the ten best innovations for Flow Builder in 2024 (according to Salesforce). This serves as a great companion piece to the roadmap article written by Alex Edelstein.

To read the full post, please click here.