6 Most Exciting New Salesforce Flow Features in Winter ’27
Salesforce Winter ’27 brings another round of improvements for people working with Flow. This time, many of the changes focus not only on building automations, but also on testing them, keeping them organized, and making it easier to manage a growing number of processes.
Here are 6 new features that, in my opinion, will be worth checking out:
New Flow Test Mode
Salesforce is changing the Salesforce Flow testing experience again! The new release introduces an even more advanced way to test Flows directly in Flow Builder. It should make it easier to validate how automations behave, test different scenarios, and improve Flow quality before deployment.
The last few releases have brought constant changes to the testing experience, which means — darn it — the “Go with the Flow” eBook needs another update again. You can find it —> HERE.
Screen Flow as a Mass List View Action
You’ll be able to launch a Screen Flow for multiple records selected from a List View or Related List.
A collection of record IDs can be passed directly into the Flow, which should make bulk operations performed by users much easier. This is pretty cool because everything will happen inside a modal, so it looks much sexier than the solutions we had to use before.
It looks good, it sounds useful, people will use it, and the world will become a better place! ;)
New Split by Date and Split by Field Value Elements
These are new ways to branch Flow logic alongside the classic Decision element. They will make it easier to send records down different paths based on dates or field values.
It’s not like these are things you couldn’t already do with a Decision element, but hey — maybe it will be nice to have another way of doing it. :) So what will be the best pattern now? Only Salesforce knows. :P
Find Unused Flow Elements
New capabilities will help identify Flow elements that are unused or don’t have descriptions. This should be particularly useful when cleaning up large and complex Flows and reducing technical debt — meaning roughly 70% of the stuff you usually have sitting around in your org. :P
Flow Tagging in the Automation App
You’ll be able to assign tags to automations, making it easier to organize and search for Flows by project, business process, team, or functional area. This should be especially useful in orgs with a large number of automations.
Of course, someone will still need to keep those tags under control, because it will be very easy to turn the whole thing into another glorious mess that nobody actually finds useful.
Time for Some Coloring
The Display Text component is getting new color picker options.
So when you’re writing a very serious warning, you can make it red. And if you’re building an advertisement for bathtub cleaner, you can make the text green. Might come in handy. ;)
Summary
Winter ’27 shows that Salesforce is increasingly developing Flow not just as a tool for building automations, but as a full platform for managing their entire lifecycle.
Testing, mass actions, better organization, and simpler logic should be especially welcome for administrators working with larger and more complex orgs.
The full Winter ’27 Release Notes should bring even more details, so it’s definitely worth keeping an eye on the upcoming information before the rollouts begin.
Peace and fLOVE!