What’s Next for Flow? Salesforce Product Manager Shares New Details On Its Future

When we caught up with Adam White, Product Manager at Salesforce, one thing stood out immediately: Flow is no longer a background tool. It has been in the spotlight for quite some time now, and is on the verge of becoming something much bigger.

Over the recent months, Flow has gone from an automation tool that’s “nice-to-have” to a “must-use” for all admins who prefer working declaratively. Now, Salesforce says they’re hearing the same question over and over again from customers: “How do we connect our tools to Flow?

And that says a lot. It means Flow is evolving – a foundational layer, even…something other tools will plug into instead of the other way around. And if you look at the roadmap, it’s clear that Salesforce is leaning into that future. Here’s where things are heading.

Flow Is Becoming Foundational

To sum it up in the simplest way possible: Flow is the now. 

For a long time, Flow was seen as just another automation option; more powerful than the rest, sure, but not always the first choice. This changed with the retirement of Workflow Rules and Process Builder. Suddenly, Flow wasn’t just an option; it became the option. 

With the help of the Migrate to Flow tool, along with significant improvements being pushed to Flow Builder with every release, customers are now moving their automations into Flow and, in the process, starting to view it as the central hub for how business processes run in Salesforce.

As AI continues to develop, Salesforce has been doubling down on Agentforce, making it a central theme at Dreamforce and across recent releases. 

Housed inside the Automation app, Action Hub gives you a central place to manage custom invocable actions across your org. You’ll be able to see a specific action’s type, description, and what processes or flows use that action. 

It’s still beta for now, but especially for orgs with complex or highly reusable automations, this kind of visibility is invaluable. It’s not quite a dependency tree, but it goes a long way toward improving observability – especially for multi-admin orgs. 

That’s one step closer to making collaboration far easier by providing a single source of truth for actions! 

AI Creeps Into Flow

When I think about AI in Salesforce, honestly, flashy demos are often one of the first things that come to mind. After all, watching a machine perform tasks that normally require human input is impressive on its own. 

But over time, AI in Flow has taken a different direction, as it’s quietly embedding itself where it can make a real difference for builders.

This started with Einstein for Flow, which brought AI assistance into everyday flow tasks like generating an initial flow or the formula for individual Formula Resources, as well as summarizing a flow to generate descriptions. More recently, it’s showing up in even subtler ways. One example: letting AI determine the outcomes of a Decision element, instead of having to manually define every branch and criterion.

That might sound like a small tweak, but it’s the beginning of something much bigger. It points toward a future where Flow can rely on AI to handle branching logic in smarter, more context-aware ways, which frees builders from some of the most time-consuming and rules-heavy parts of automation design.

Making Flow Enterprise-Grade

Finally, this is all one big push to make Flow feel more at home in enterprise environments. When you think “enterprise”, you think large-scale customizations, critical automations, processes that impact thousands of users, and of course – strict security and compliance requirements. 

With the stakes raised, it means there’s no room for half-baked testing or unclear deployment practices. Big businesses can’t afford to roll out a feature without thorough testing first, and when issues do arise, they need to be handled with tools that can actually keep up with monitoring, troubleshooting, and collaboration.

The advancements in this release are all moving in that direction, and Salesforce has made it clear they’re not slowing down. Looking ahead, the future focus may include:

• Adding siloed test data (a gap Flow had compared to Apex).
• Adding tools for collaboration, so orgs that have multiple admins can work on automation without clashing. The version comparison tool is already a nice advancement towards this.
• Building in stronger governance and monitoring.
• Exploring agentic orchestration, as in coordinating multiple users, processes, and even “human-in-the-loop” agents inside Flow.

Flow is on the way to making itself as powerful and reliable as Apex, only more approachable to admins and without the barrier of code.

Final Thoughts: Looking Ahead

Between richer screen Flow experiences, a true testing experience, improved debugging, Action Hub, and practical AI features, Salesforce is reshaping what Flow and automation can do on the platform. I was reminded of this during the recent Flow vs. Apex throwdown webinar, which was an exciting (and surprisingly entertaining) showcase of how far Flow has come. (No spoilers, but let’s just say Flow held its own.)

The message for admins and architects is clear: if you haven’t already, now is the time to double down on Flow because it’s no longer just one option in the box; it’s become the box itself.