10 New Salesforce Flow Features in Spring '26

If you've been building Screen Flows for any length of time, you know the frustration. You want a simple Kanban board? Custom component. Inline-editable data table? Custom component. A styled message banner? Yep, custom component. It felt like every decent UI pattern required Lightning Web Components or an AppExchange install just to get something that should've been native.

Well, Spring '26 finally changes that. Salesforce dropped a batch of Flow enhancements that honestly feel like the team has been reading our wish lists. I've been testing these in my sandbox for the past few weeks, and some of them are going to save admins serious time. If you're not familiar with some of the terminology I'll be throwing around, salesforcedictionary.com is a solid quick-reference for Salesforce terms and concepts.

Let's get into the ten features worth knowing about.

Kanban Board Component for Screen Flows

This one got people excited the moment it hit the release notes. You can now drop a native Kanban Board component directly into your Screen Flows. Think of it like the standard Salesforce Kanban view you see on list views, but embedded right inside a flow screen.

It's great for things like case management workflows, project tracking, or onboarding checklists where users need a visual way to see record status at a glance. Right now, the component is read-only - you can't drag cards between columns yet - but even in its current state, it replaces a lot of custom LWC work that admins were leaning on developers for.

I expect Salesforce will add interactivity in a future release. For now, it's still a win for anyone building internal tools with flows.

Inline-Editable Data Tables

This might be the single most requested Flow feature I've seen in the community over the past two years. Data Tables in Screen Flows now support inline editing directly in the component - no third-party solutions needed.

Currently, inline editing works with Text-type fields, and changes get captured immediately within the flow context. It's not full CRUD on every field type yet, but it covers a huge number of use cases. Think bulk-editing contact names, updating notes fields across multiple records, or letting users correct data right inside a guided process.

Before this, you either needed a custom LWC, an AppExchange component, or some creative workaround involving loops and individual edit screens. None of those were great. This native solution is cleaner and way easier to maintain.

Custom Styling for Flow Screens

Salesforce added a new Style tab in Flow Builder that lets you customize colors across your screen components. You can modify button colors, borders, backgrounds, and text throughout your flow screens.

On top of the screen-level styling, individual components like Text, Number, Date, and Date/Time fields now have their own color properties too. So if you need a specific input field to stand out - say, a required date field highlighted in your company's brand color - you can do that without CSS hacks.

One limitation to know about: you can't use variables or formulas to drive the color values dynamically. Everything is set at design time. Still, for teams that have been pushing for branded, polished flow experiences, this is a big step forward.

Message Component for Screen Flows

Here's a small but genuinely useful addition. The new Message component lets you display styled banner messages directly in your Screen Flows. You pick a message type - Info, Success, Warning, or Error - write your text, and it renders as a clean, accessible notification banner.

Before this, showing contextual messages in a flow screen meant either using Display Text with manual formatting (which never looked great) or, again, building a custom component. The Message component just works out of the box and follows Salesforce's Lightning Design System patterns, so it looks professional without any extra effort.

I've already started using it for things like showing validation warnings before users submit a form, or displaying a success confirmation on the final screen of a multi-step process.

Collapsible Decisions and Loops

Anyone who's built a flow with more than five or six Decision elements knows how fast the canvas gets messy. Spring '26 introduces the ability to collapse Decision and Loop elements on the Flow Builder canvas.

Click to collapse, click to expand. That's it. Simple feature, but the impact on readability is huge. When you're debugging a complex automation that has nested branches going three levels deep, being able to fold up the sections you're not working on makes a real difference. It's one of those quality-of-life improvements that doesn't sound exciting on paper but you'll use constantly.

Scrolling Support on the Flow Canvas

This one is almost embarrassing that it took this long, but I'll take it. You can now use your mouse scroll wheel to navigate the Flow canvas. Previously, you had to click and drag, or some people installed Chrome extensions just to get basic scrolling to work.

It sounds minor. It's not. If you spend hours a day in Flow Builder, this removes a constant small friction that added up over time.

Record-Triggered Flows for Files

Spring '26 adds ContentDocument and ContentVersion as supported objects for Record-Triggered Flows. That means your flows can now fire automatically when files are uploaded, updated, or created in Salesforce.

This opens up a bunch of automation possibilities: automatically tagging files based on naming conventions, notifying a team when a document gets uploaded to an opportunity, triggering an approval process when a contract file lands on an account. Previously, you needed Apex triggers to handle file-related automation. Now admins can do it declaratively.

If you're working with file automation and need to brush up on how ContentDocument vs. ContentVersion works, the breakdown on salesforcedictionary.com is helpful for understanding the object relationships.

Debug Values Persist Between Runs

When you debug a flow, you typically have to re-enter all your test input variables every single time. If your flow has ten input variables, that's ten fields you're filling out over and over while iterating on logic.

Spring '26 fixes this by persisting your debug input values between runs. Make a change to your flow, hit debug, and your previous test values are still there. It's a small thing that saves a surprising amount of time when you're deep in a testing cycle.

Flow Logging in the Automation App

Flow execution logs are getting a proper home. There's now a dedicated tab in the Automation App that consolidates flow run metrics using Data 360. Instead of hunting through debug logs or setup pages, you get a centralized view of how your flows are performing - run times, error rates, execution counts.

For orgs running hundreds of automated flows, this kind of visibility is essential. It makes it much easier to spot flows that are failing silently or running slower than expected. If you're responsible for flow governance at your org, this is the feature to pay attention to.

AI-Powered Flow Building with Agentforce

Last but definitely not least, Spring '26 brings what Salesforce is calling "vibe-flow building" with Agentforce integration. You can now use natural language to iteratively build and modify flows. Describe what you want in plain English, and Agentforce generates or modifies the flow accordingly.

It works similarly to how AI coding assistants handle code generation - you give it instructions, it produces a draft, you refine with follow-up prompts. The AI-powered draft flow capability is now generally available, and the iterative refinement through Agentforce is the real addition here.

I'll be honest: I was skeptical about AI-assisted flow building when it was first announced. But after trying it, I can see it being useful for scaffolding out the basic structure of a flow quickly, even if you still need to fine-tune the details manually. It won't replace understanding how flows work, but it does speed up the initial setup.

What This Means for Admins

The pattern here is clear. Salesforce is making Flow the go-to tool for basically everything that used to require code or third-party components. Between the Kanban boards, editable data tables, custom styling, and native file triggers, there's less and less reason to jump to LWC development for common UI patterns.

If you're an admin who's been putting off learning Flow, now's the time. And if you're a developer, don't worry - there's still plenty of complex work that needs code. But the bar for when you need to write that code keeps moving higher.

For a complete glossary of Flow-related terms and Salesforce concepts mentioned in this post, check out salesforcedictionary.com.

What's your favorite feature from this list? Have you tried any of these in your sandbox yet? Drop a comment - I'd love to hear what's actually making a difference in your day-to-day work.