Summer '25 adds a Flow Builder action that drafts an autolaunched Flow Approval Process straight from a screen flow, so a multi-level approval no longer starts from an empty screen.
Overview
The action is called Create Flow Approval Process. You gather input in a screen flow, hand it to the action, and the action drafts an autolaunched flow approval process with up to 20 levels of approval, final actions, and a recall path. Open the draft in Flow Builder afterwards and work through the individual elements.
Key benefits
- Users can draft an approval process from a flow instead of waiting for someone to build one by hand.
- Approval chains can run up to 20 levels deep.
- Final actions and recall paths are in the draft, so the whole approval lifecycle is covered from the start.
- Everything stays in Flow Builder, so admins and builders do less jumping between setup screens.
How it works
Capture the inputs you need in a Screen Flow. Add the Create Flow Approval Process action element and pass those values in. You get back a draft autolaunched flow approval process, which you can open and configure in Flow Builder. The draft can hold:
- Up to 20 approval levels
- Final actions
- A recall path for submitters
Best practices
- Have the screen flow validate and collect every piece of metadata the approval steps need: approvers, routing rules, criteria.
- Name things descriptively. Generated drafts are hard to pick out of a Flow Builder list otherwise.
- Test in a sandbox or Developer Org before you enable this in production, and check routing, final actions, and recall behavior while you are there.
- Write down any customizations or org-specific limits so stakeholders know what they are working with.
Use cases
This earns its keep when business users need a structured approval and do not want to wait for an admin to build one by hand. Common scenarios:
- Sales teams drafting territory-specific approval chains for discount requests.
- HR teams creating position or compensation approvals that vary by department.
- Procurement workflows that need multi-step vendor approvals and a final acceptance action.
References
Official Release Note: Create Flow Approval Process action (Summer '25)
Conclusion
Letting a flow draft the approval process closes the gap between what a user types into a screen and the automation somebody has to configure afterwards. Admins do less manual setup and developers get a scaffold to build on, while the business user who needed the approval can start it themselves and let the platform team finish it.
Leave a Comment