You set the trigger when you create a new flow in Flow Builder. The first screen asks what should start the flow, and your answer locks in the trigger type and the elements you can use. Here is the path for a record-triggered flow, the most common automation choice.
- Open Flow Builder and create a flow
In Setup, go to Flow under Process Automation and click New Flow. Flow Builder opens the template chooser, which lists the trigger types you can start from.
- Pick the trigger type
Select Record-Triggered Flow for a DML-based automation, or pick Screen Flow, Schedule-Triggered Flow, Platform Event-Triggered Flow, or Autolaunched Flow for the other patterns. This choice is hard to undo, so confirm it before drawing elements.
- Choose the object and the trigger event
For a record-triggered flow, select the object, then choose whether the flow runs on create, on update, on create or update, or on delete. This is the DML event that fires the flow.
- Set entry conditions and the run timing
Add entry conditions so only matching records start the flow. Then choose Fast Field Update to run before save, or Actions and Related Records to run after save. Set the optional trigger order value if other flows share the object.
- Build, save, and activate
Add your elements, save the flow with a clear name, then activate it. An inactive flow will not run on the trigger even after you save it.
Runs on a create, update, or delete on one object. Offers before-save (Fast Field Update) and after-save timing.
Runs when a user launches it from a button, action, page, or URL. The only type that allows Screen elements.
Runs on a set schedule against a batch of records, as the Automated Process user, in async context.
Runs once per published platform event message, for event-driven and decoupled designs.
Runs only when called by Apex, the REST API, a button, or a parent flow as a subflow. No screens allowed.
- The trigger type is locked at the first save. Switching it later forces Flow Builder to drop elements that the new type does not support.
- Before-save flows cannot call Apex actions, update related records, or send emails. Use after-save for any of those.
- Schedule-triggered and platform event-triggered flows run as the Automated Process user, so check that user has access to every object and field the flow touches.
- Saving a flow is not enough. It must be activated before it will run on its trigger.