You want to Flow type Watch for
Change fields on the record being saved Record-triggered, optimised for Fast Field Updates Runs before the save, so it's quick, but it can only update that same record.
Create or update related records, send email, call an action Record-triggered, optimised for Actions and Related Records Runs after the save. This is where most old Process Builder logic ends up.
Do something days after a change, such as a renewal reminder A scheduled path on a record-triggered flow This replaces time-dependent workflow actions. Base the timing on a date field, not on when the record was saved.
Guide a user through a form or a multi-step task Screen flow Launched from a button, a Lightning page or a utility bar. It runs as the user, with their permissions, unless you set it otherwise.
Check a batch of records every night or week Schedule-triggered flow Filter the records in the start element. Sweeping a whole object every night can hit limits as the org grows.
Reuse logic from several places Autolaunched flow (no trigger), called as a subflow or from Apex Keep its inputs and outputs few and clearly named so other flows can call it safely.