Salesforce Summer '26 Flow Builder: 10 Features Admins Will Love

Preview orgs for Summer '26 went live on April 16, and I've been spending every evening this week poking around Flow Builder to see what's actually changed. The short version? This is one of the most admin-friendly Flow releases I've seen in a while. Salesforce spent a lot of time fixing the little paper cuts that make you want to throw your keyboard at 2pm on a Friday.

If you've been holding off on upgrading your Flows, or if you still have a few ancient Workflow Rules and Process Builders limping along, Summer '26 gives you some real reasons to finish that migration. I'll walk you through the features I think actually matter, why they matter, and where the trapdoors still are.

Why Summer '26 Feels Different

Salesforce has been iterating on Flow Builder for years, but the pattern I've noticed lately is a shift from "add more capabilities" to "clean up what's there." Summer '26 fits that trend. A lot of the improvements are about visibility, debugging, and reducing the number of clicks it takes to do something you do every day.

Before getting into specifics, one housekeeping note: preview org registration opened April 16. If you haven't signed up yet, go do that first. Testing in a sandbox that's on the same version as production is good, but testing in an actual preview org is how you catch the weird edge cases before your users do. And if you stumble on a term you don't recognize while poking around, salesforcedictionary.com is a decent place to look things up without having to wade through twelve tabs of release notes.

1. Collapsible Fault Paths and a Cleaner Errors Panel

This one's small but it genuinely makes me happy. In Summer '26, Fault Paths can now be collapsed, which means your giant record-triggered flow doesn't become a spaghetti diagram every time you add proper error handling.

The Errors and Warnings panel also got reorganized. Instead of a flat list that scrolls forever when you have a messy flow, errors now show up as cards. Each card has the specific element, the error description, and a link that takes you right to the problem. I clocked myself debugging a broken flow in the preview org versus the same kind of flow in our current production version, and the preview was noticeably faster, maybe 30% less clicking around.

This builds on the Spring '26 work that made Decisions and Loops collapsible. The net effect: flows are easier to read, easier to present in screen shares, and easier to hand off to the next admin.

2. New Date Field Operators (Finally)

Date handling in Flow has always been fiddly. You'd write some formula that computes "today minus 30 days" and then cross your fingers that time zones don't mess things up. Summer '26 adds a batch of new operators specifically for date fields:

• Is Today
• Is Tomorrow
• Is On
• Is In The Next N Days
• Is On Anniversary Of

That last one is sneakily powerful. If you've ever built a birthday reminder flow or a contract renewal nudge, you know the dance of extracting month and day, comparing them, handling leap years, etc. Now it's one operator. I've already got a renewal reminder flow in my backlog that's going to be about four elements simpler once Summer '26 drops.

3. Global Flow Resources

This is the feature I've been waiting for. You can now define value mappings once as Global Flow Resources in the Automation app and reference them across any flow that supports the Transform element.

In practice: suppose you have 12 different flows that all need to standardize country codes from external systems. Currently, you either copy the mapping into every flow or build some shared custom metadata jig. With Global Flow Resources, you define the mapping once, and every flow can reference it. Change it in one place, and every flow picks up the new version.

I'm already planning to consolidate our lead source normalization logic into a single Global Flow Resource. We have at least six different flows touching lead source values, and every time marketing adds a new campaign type, someone has to remember to update all six. That kind of knowledge-in-someone's-head problem is exactly what this feature solves.

4. Data Table Shows Names Instead of Record IDs

If you've ever built a screen flow with a data table that includes a lookup field, you know the problem: instead of showing the account name, the column shows 0015g00000XYZABC. Users are understandably confused. You'd then build some goofy formula field or extra query to resolve the ID to something human-readable.

Summer '26 fixes this. In the Data Table component, there's now a checkbox on lookup columns that says "Display record name and make clickable." Check it, and the column shows the account name. Click the name, and the user is taken to that record.

This is the kind of fix that tells me someone on the Flow team actually uses Flow. It's a small feature, but it removes the single most common workaround I see in screen flows. Quick aside: make sure your users have read access on the looked-up object, otherwise they'll just see a blank cell.

5. Custom Batch Size for Record-Triggered Flows

For anyone who has ever had a flow tip over because a bulk import hit an Apex governor limit in some subflow, this is for you. Summer '26 lets you set a custom batch size for record-triggered flows, down from the default 200. If your flow has some heavy logic (callouts, big subflow invocations, chatty SOQL), smaller batches reduce the odds of hitting CPU or DML limits.

My rule of thumb: if you're doing anything with a callout, start at 50. If you've got a Transform or a subflow with its own processing, try 25. You'll trade a bit of throughput for a lot of stability, which is almost always the right call for production flows.

6. Value Mapping in the Transform Element

Tied to the Global Flow Resources news above, the Transform element itself got smarter about value mapping. You can now standardize values from one collection to another directly inside Transform without needing an intermediate Decision element or a formula tree.

Say you're pulling lead data in from a third-party tool and their "industry" values don't match your picklist. Pre-Summer '26, you'd have a decision tree with 15 branches mapping "Software Development" to "Technology," etc. Now you define the mapping once (or reference a global one) and Transform handles the substitution.

7. Radio Button Group Component

Small but nice: there's now a proper Radio Button Group component in screen flows. Before, you had to fake it with a picklist and some CSS contortions if you wanted actual radio-style UX. The new component handles keyboard navigation properly, has built-in validation, and plays nicely with accessibility readers.

8. Natural Language Edits for Screen Flows via Agentforce

Agentforce can now help you edit Screen Flows using natural language. Previously, natural language editing worked for Record-Triggered and Schedule-Triggered flows, but Screen Flows were left out. Now they're in.

I'm going to be honest: I'm somewhere between intrigued and skeptical on this one. The demos look great ("add a new screen after the contact lookup that asks for a reason"), and for simple edits it probably works well. But I've seen AI-assisted flow editing generate confidently wrong logic enough times to know I'm going to review every single change before saving. Still, for the "add a text field to this screen" type of tweaks, it'll probably save me 20 seconds here and there, which adds up.

If you're new to Agentforce and trying to keep the terminology straight, salesforcedictionary.com has a pretty clean explanation of how Agentforce, Einstein Copilot, and Prompt Builder relate to each other, which was useful when I was first wrapping my head around the difference.

9. Email Template Deployments Don't Break Flows Anymore

Small but meaningful. Historically, if a flow referenced an email template and you deployed that flow to another org, the email template reference would sometimes break, showing up as a null reference or a deploy error depending on how lucky you felt. Summer '26 fixes the underlying metadata handling so email templates resolve properly across environments.

This has been a persistent headache for teams that have separate dev, QA, UAT, and production orgs. If you've got a CI/CD pipeline that involves deploying flows, this removes one more failure mode from your Friday afternoons.

10. Better Flow Testing Coverage

Flow testing finally got some love. The Flow Test framework now supports more element types, and you can assert on collection variables and record variables properly. It's still not a full replacement for the kind of testing I'd want for a mission-critical flow, but it's good enough that I'm actually going to write tests for my record-triggered flows in Summer '26 instead of the half-hearted approach I've been getting away with.

If your org is moving toward Flow as the automation tool of record (and you should be), setting up Flow Tests as part of your deployment pipeline is genuinely worth the hour it takes to learn the syntax.

What to Test First in Your Sandbox

My priority list for Summer '26 preview testing, in order:

First, test any flow that uses lookup fields in Data Tables. The name-display feature is almost certainly what your users will notice first. Second, test your bulk-processing flows with different batch sizes. Third, if you're heavy on email templates in flows, run through your deployment pipeline end to end. Fourth, if you use Transform elements, look at where Global Flow Resources could clean things up. Fifth, poke at the Agentforce natural language editing for Screen Flows and form an opinion.

Wrap-Up

Summer '26 isn't a flashy release. It's a release for people who spend their days actually building and maintaining flows, and I mean that as a compliment. The new operators, the UI cleanup, the Data Table fixes, the batch size control: these are all things that will quietly save time every single week. That's better than a splashy feature you use twice and forget about.

If you're still using Process Builder or Workflow Rules for anything important, Summer '26 is another nudge toward finishing that migration. Salesforce has been clear that Flow is the future, and the feature gap between Flow and the older tools is now big enough that there's not much excuse to stay behind.

I'm curious which of these features you're most excited about, and if there's anything you're finding in preview that I missed. Drop a comment and let me know. If you hit anything weird in your testing, I'd genuinely like to hear about it before we all upgrade production.

---

For more Salesforce terminology, release tracking, and admin resources, check out salesforcedictionary.com - it's my go-to reference when someone mentions a term I only half-recognize.