Autolaunched versus record-triggered Flow Approval processes
Key Takeaway
Use an autolaunched flow approval process when a user, another process or an external system decides when to submit. Use a record-triggered flow approval process to start the approval automatically when a record changes.
A flow approval process sends a record through stages of approval steps that you build in Flow Builder. Its type controls how it starts and who can start it.
What starts the approval
Pick the type by asking what starts the approval and how much control you need over when it runs.
| Autolaunched flow approval process (No Trigger) | Record-triggered flow approval process | |
|---|---|---|
| How it starts | It waits for someone or something to submit the record. | It starts on its own, but only when a record is created or updated and meets the entry criteria. |
| Use it when | Users start approval requests manually, or another process or external system decides when to submit. | You want to start the approval automatically when a record changes, with no user action to submit. |
| It fits | Cases where a user decision or a complex condition controls submission, not just a record save | Compliance or review workflows where a record meeting certain criteria always needs approval |
| Example | A sales rep submits a discount request after deciding the deal needs approval. | A large expense report, or an opportunity discount over 20% that needs manager sign-off |