It's been a while since I sat down and wrote a proper release update post just for Flow. Agentforce has taken up most of my bandwidth lately (and rightfully so — it's an exciting time), but every release season I still go back and dig through what's new for Flow first. It's where I started, and it's still where a huge chunk of the actual work happens under the hood of every agent, every automation, every "how did they build that" moment on this platform.
So here we are — Winter '27, and eight updates I think are genuinely worth your time.
Want to explore these features before your own org gets them? Sign up for a Winter '27 Pre-Release org and get hands-on access right away — that's how I put this post together.
As for production: Winter '27 is rolling out in three waves — August 29 (already live for a first set of instances), and October 3 and October 10, 2026 for everyone else. If you haven't gotten it yet, you're most likely on one of the October dates. Check your exact rollout date on Salesforce Trust by searching your instance name (found under Setup → Company Information).
1Split Flow Paths by Date or Field Value Without Expressions
If you've ever built a Decision element just to route based on "is this date in the past" or "is this picklist value X," you know the mild annoyance of reaching for a formula for something that simple. Now you don't have to. The new Split by Date and Split by Field Value decision types let you pick a field, define your paths, and configure values through inline pickers — no expression required.
This is a small change on paper but a real quality-of-life win, especially if you're building flows with admins or marketers who aren't comfortable writing formulas but understand "if this date is before today, do X" perfectly well.
Say you're routing Accounts by company size. Using Split by Field Value on the Employees field:
Enterprise Account — Employees is greater than or equal to 1,000 → set Description to "Enterprise Account" Standard Account (default path) → set Description to "Standard Account"
2See More of Your Flow with a Denser Canvas
The Flow Builder canvas is more compact now, so you can actually see more of your flow without the constant scroll-and-zoom dance. Element cards show their type and API name in a tooltip instead of taking up permanent visual space, and the End element is now just an icon instead of a full card.
If you build anything beyond a handful of elements, you know how much time gets lost just navigating the canvas. This won't make your flow simpler, but it will make it easier to actually see the shape of what you built.
3Track Flow Changes Over Time with Edit History
This is the one I'm most excited about. Edit History gives you a timeline of every save on a flow, lets you preview what changed at the element level, and lets you restore a previous version — either as a new version of the same flow or copied into a separate flow entirely.
Anyone who has ever opened a flow that "used to work" and had to guess what changed and when will understand immediately why this matters. No more relying on memory or debug logs to reconstruct what happened — it's just there.
4Clean Up Flows Faster with the Unused Resources Filter
A small one, but a satisfying one. The Toolbox now has an Unused filter that narrows the resource list down to variables, formulas, and other resources with no recorded usage — perfect for when you're cleaning up a flow that's grown messy over time. Note it's auto-layout only for now.
5See Agent Actions and Tools Without Leaving Flow Builder
This is where Flow and Agentforce start to overlap, and I think it's a sign of where things are headed. When you select a Run Agent element and choose an agent, you can now expand its information panel right there in Flow Builder to see the agent's assigned actions — name, type, description, API name — without jumping over to Agentforce Builder.
If you're troubleshooting a flow someone else built, or trying to understand what an agent can actually do before you wire it into your automation, this saves a real context switch. Small feature, but it's exactly the kind of bridge I want to see more of between these two tools.
6Catch Missing Required Fields When You Save a Flow
Flow Builder now warns you at save time if a Create Records element using a record variable is missing an assignment for a required field. Previously you'd only find out when the flow actually ran — and failed. Now it shows up in the validation panel before you even test it.
Worth noting: this only catches what it can determine at design time. If a required field gets populated through an input variable or a subflow, you won't see the warning until runtime — so this isn't a total safety net, but it will catch a lot of the careless mistakes before they become 2am debugging sessions.
7Capture Time Values with the Time Component
A dedicated Time component for screens, useful for anything involving scheduling — service appointments, reservations, anything where you need a clean time input rather than a workaround. You can set a label, default value, placeholder text, and min/max time values right in the properties panel, then use the output elsewhere in your flow.
Simple, but it's one of those "finally" features — this has been a gap for a while if you've ever tried to build a scheduling flow without it.
8Test Flows in a Dedicated Test Mode (Beta)
Saving the biggest one for last. Test Mode lets you build and test your flow in the same place, and — this is the part I really like — save test scenarios so you're not manually re-entering inputs every single time you want to check something.
You can run a one-off test to chase down a specific issue, then save that setup to reuse later. Or go further with Scenario Testing Automation: add assertions (conditions that check expected results), and your saved scenario will report pass or fail on demand. That's real regression testing for flows — confirm it works now, and confirm it still works after your next change.
It's in beta, so it's subject to Salesforce's Beta Services Terms, and you'll need to turn it on first: Setup → Process Automation Settings → Flow Test Mode (Beta). Once it's on, hit Test inside Flow Builder to get started.
This is the update I think has the most long-term impact on how we build. Flow testing has always been the thing everyone knows they should do more of and rarely has a good workflow for. This is Salesforce actually addressing that gap.
That's my top 8 for Winter '27. If you explore your pre-release org and find something I missed that deserves a spot on this list, I'd genuinely love to hear about it — drop it in the comments or find me on LinkedIn.
Flow's still where I started, and it's clear from this release that it's not done growing.
.png)
.png)
.png)
.png)
.png)
.png)
0 Comments