Record-Triggered Flow

⚡ 1-Minute Summary Follow the hierarchy: Start with simple configuration, then move to Flow, and only use Apex when strictly necessary. Choose the right trigger context: Use before-save to update fields on the record being saved. Use after-save when updating related records, sending notifications, or running async paths. Protect your governor limits: Never place queries or DML statements inside loops. Collect records into collections and execute a single DML operation outside the loop. Module Map: The Complete 360° Automation Architecture MODULE ROOT: 'Which automation tool should you use, and will it survive bulk processing?' ├── Flow Types: 5 core flavors for 5 distinct execution contexts ├── Flow vs. Apex Decision Matrix: Complexity and governor limits threshold ├── Bulkification & Recursion Guards: Preventing the #1 Flow failure mode ├── Before-Save vs. After-Save Cost: Zero extra DML vs. an additional save cycle...

In plain words: Salesforce Flow is Salesforce's flagship low-code automation engine. It lets administrators and developers build guided, interactive user wizards (Screen Flows) and automated backend logic (Record-Triggered Flows) using a visual drag-and-drop builder—handling complex database updates, decisions, and external integrations without writing Apex code. With the retirement of legacy automation tools like Workflow Rules and Process Builder, Salesforce Flow is the primary declarative automation framework on the Salesforce platform. It combines visual point-and-click usability with the power of full programming concepts—including branching decisions, loops, collection sorting, transaction rollbacks, and external REST API callouts. 1. The Core Types of Salesforce Flows Salesforce Flow Builder provides several specialized flow types designed for distinct execution contexts: Screen Flows: User-interactive wizards that present forms, collect...