As a Salesforce Admin, you and your business users are probably familiar with back-office processes you would love to automate. Like the vendor onboarding workflow that starts in Salesforce, jumps to email for document collection, touches an ERP nobody has API access to, and ends when someone manually updates a spreadsheet to say it’s done. Or the invoice review process where an approver has to pull a PDF, open a second system, cross-reference a third, and then come back to Salesforce to act. While these processes keep the business running, they’re also the ones nobody has fully automated as they’re locked behind human interactions, email, and documents.
Agentforce Operations was built for this. Formerly known as Regrello and generally available (GA) as of April 2026, Agentforce Operations extends automation to the back-office processes that have always been hard to reach, giving powerful tools to your business users to work more efficiently with agents.
The two things your users will work with most are blueprints and workflows. A blueprint is the reusable template for a process: every step, who’s responsible, what data is required, what decisions get made, and what happens next. A workflow is a specific execution of that blueprint — one instance of the process running from start to finish.
Under the hood, when you generate a blueprint from a document, the AI produces a Declarative DSL (Domain Specific Language), a structured definition of your process that the platform’s process engine reads and executes. Users won’t interact with the DSL directly, but they may see it referenced in technical documentation.
There are three ways to create a blueprint.
Most teams start with the AI generation path and refine from there.
Thirty-plus prebuilt blueprints cover the most common back-office processes: invoice auditing, supplier onboarding, purchase order rescheduling, warranty claims, contract review, and more.
The blueprint breaks the process into logical stages and assigns each task to the right resource: a human owner or a specific AI agent. Accountability is built in from the start. You can review the exact instructions each agent runs and customize them to match your requirements without touching code.
Once the blueprint exists, triggering a workflow is straightforward. A team member sends an email to a designated Agentforce Operations address, and the system creates a new workflow instance automatically. You can also kick one off directly in the UI or via API. The agent starts working immediately: validating inputs, extracting data from documents, reaching out to external contacts by email, and updating the workflow as each step completes.
External participants, like a supplier providing qualification documents, respond by email. They don’t need a login or access to any system. The agent handles the coordination and logs every action, so you can see exactly what happened and when.
When a task is assigned to both an agent and a human reviewer, the agent prefills the data and the human reviews and submits. If an agent can’t complete a task, it automatically reroutes to a fallback assignee you configure. You can see exactly how an agent solved a problem, or where it got stuck, by opening the Task Activity pane, which shows the agent’s planned approach and each execution step.
A few edges to plan around: Agents can’t fill signature fields, refer to people by name (only email addresses), or follow URLs embedded in documents.
The home dashboard shows every workflow in flight: status, current stage, task owner, and any bottlenecks flagged automatically. When something stalls or an agent gets overridden consistently, you can see it. Business users can update the blueprint in plain language without a developer or a change request. When you publish an updated blueprint, running workflows are not affected. They stay pinned to the version they started with. Only new workflows pick up the change.
The best way to understand Agentforce Operations is to see it run. Here’s an overview of a supplier qualification process from blueprint to completed workflow.
From a single email, an agent picks up the work, coordinates the steps, and hands off to a human only when a decision is needed.
Agentforce Operations is a platform that helps automate your back-office processes, coordinate your documentation, and use agents while still keeping humans in the loop.
Flow handles structured automation within Salesforce. Agentforce Operations reaches what lives outside it: external systems, documents, email, and human approvals that happen off-platform. They complement each other. Flow handles the Salesforce-native steps. Agentforce Operations handles the rest of the process.
High-volume, repeatable processes with multiple steps and handoffs across systems and people. Common examples include invoice auditing, vendor onboarding, purchase order management, contract review, and internal approval workflows. If it currently lives in a spreadsheet or runs on email, it’s a candidate.
No. Blueprints are built using natural language and existing documentation. Business users can modify and improve processes as they run, without IT involvement. The initial setup requires process knowledge more than technical skills.
Pick one process that’s repetitive, measurable, and currently relies on manual workarounds. Do the process mapping before you open the product. Know which steps the agents will handle and which ones still need a human. A well-scoped starting process makes the proof of concept faster and the results clearer.
Let’s be real for a minute. Things are moving incredibly fast right now. Every time you log in or refresh your feed, there’s a new AI tool popping up, promising to change how we work. If you’re feeling the fatigue of constantly trying to keep up, or if you’re quietly worrying about where your traditional […]
Today on the Salesforce Admins Podcast, we talk to Kacie Molina, Salesforce Consultant at Kawaii Cloud. Join us as we chat about how admins can start small with Agentforce and still make a big impact. You should subscribe for the full episode, but here are a few takeaways from our conversation with Kacie Molina. Why […]
Think about the last time you had to solve a user access riddle: Pam and Jim are in the same department, so why can Pam edit Dwight’s record but Jim can’t? That kind of troubleshooting could take dozens of clicks and cost hours of your day. Now, imagine asking Salesforce and it solves it for […]
