In this video, I break down a genuinely big piece of Flow news: Salesforce has removed the paywall on Flow Orchestration and made it a standard Flow type. That means you can now build orchestrations as part of core Flow—no separate add-on, no extra licensing cost, and (importantly) no more usage-based cap like the old “600 free orchestration runs per year” limit. If you’ve been curious about Orchestration but kept hitting cost or access hurdles, that excuse is gone. I also walk through what Flow Orchestration actually is in practical terms. Standard flows are great for single-step automations, but real business processes often involve multiple people, multiple departments, and a specific sequence—think employee onboarding where HR, IT, and managers all need to complete steps in order. Orchestration lets you design that whole connected process in one place, instead of stitching together a messy web of separate flows and hoping they behave. From a career angle, this is huge: it lets admins and consultants own complex, cross-team automation end-to-end, bringing more value in scoping meetings and job interviews. To get started, open Flow Builder and you should now see orchestration flow types available to create and test in your org.