Agentic Orchestration
The AI reasons and decides. Flow actions determine the work, with repeatable outcomes.
TL;DR
- The user problem
- How I led
Reuse as the design philosophy, build an action once, and teams and agents reuse it.
- Business outcome
Agentforce passed $1B a year. Flow runs 461 billion times a month.31
Apex and Flow become actions an agent can call
Topics, actions, a live build from a blank slate
Plain language to a working flow
Where every invocable action lands
monthly Flow executions
Salesforce Engineering: Flow generation across 461B monthly executions, 2026agents per customer, up from 5 in a year
Salesforce Agentic Enterprise Index, second edition, 2026more agent actions per customer, every month
Salesforce Agentic Enterprise Index, second edition, 2026faster to draft a flow: 10 minutes to 10 seconds
Salesforce Engineering: Agentforce for Flow, 99% faster, March 2025User problem
Admins won’t ship an agent they can’t predict. Agentforce reasons. The system of record needs the same result every time. That’s where automation becomes critical: turning probabilistic intent into governed, predictable execution.
My role
Create an easy way to transform deterministic workflows that already exist in the enterprise into trusted, repeatable actions that an agent can execute.
How I led
Designed and shipped Action Hub, a library of actions that is easy for everyone to use and manage across the lifecycle. Build an action once, and every agent and user can reuse it with confidence.
Reuse, don’t rebuild
Any existing automation becomes an agent action.
Clear instructions first: metadata descriptions in each action call
Agents pick actions by reading them, so the description comes first.
See and manage every step of the action lifecycles and their dependencies
Admins can observe and test agents before launch and trace every step after.
Business outcome
Flow became the backbone of how Agentforce gets work done, driving adoption by 55.1% in 12 months.
Revenue
$1B+ a year. Agent work up 111% in one quarter.3
What the teams shipped
Set up an agent and test it in a chat before it goes live.
Salesforce Admins: the new Agentforce Builder ↗Run hundreds of test questions before launch.
Salesforce Admins: the new Agentforce Builder ↗Turn an existing automation into something an agent can do.
Salesforce Admins: custom actions best practices ↗One line of code makes a developer’s work available to agents.
Agentforce Developer Guide: Apex InvocableMethod actions ↗Call an agent as one step of a bigger process.
Salesforce Developers: invoke agents with Apex and Flow ↗Describe a flow’s inputs and outputs, and an agent can use it.
Trailhead: add a flow as an agent action ↗Write what you want in plain English; get a working flow.
Salesforce Engineering: Flow generation across 461B monthly executions ↗A record of every run: how long, and what went wrong.
Spring ’26 release notes: Flow ↗Agents reach systems outside Salesforce.
Salesforce Ben: everything you need to know about MuleSoft for Agentforce ↗Sources
- Salesforce Engineering: Flow generation across 461B monthly executions2026
- Salesforce Engineering: Agentforce for Flow, 99% fasterMarch 2025
- Salesforce Q1 FY27 results27 May 2026
- Salesforce Agentic Enterprise Index, second edition2026
- Agentforce Developer Guide: actions
- Agentforce Developer Guide: Apex InvocableMethod actions
- Trailhead: add a flow as an agent action
- Salesforce Admins: custom actions best practices2024
- Salesforce Developers: invoke agents with Apex and FlowApril 2025
- Salesforce Admins: the new Agentforce Builder2026
- Spring ’26 release notes: Flow2026
- Salesforce Ben: everything you need to know about MuleSoft for AgentforceApril 2025