Welcome to Trailblazer Talk! In this episode, we—Ethan Parker and Sophia Bennett—are diving into the world of Salesforce Flow, exploring the distinct roles and responsibilities of developers versus admins. Inspired by Andrew Cook’s insightful article, we break down how Flow Builder and Apex coding complement each other and how both roles contribute to optimizing your Salesforce environment.

Here’s what we will cover:

• Understanding Salesforce Flow: We’ll start by explaining what Salesforce Flow is and how it automates tasks like sending emails, creating records, and updating data. Learn how Flow Builder makes automation accessible even for those without coding experience.
• Developer vs. Admin Responsibilities: We’ll discuss the key differences between developers and admins when working with Salesforce Flow. Discover which types of flows are better suited for each role, from simple Screen Flows for admins to more complex Autolaunched Flows for developers.
• Types of Flows Explained:
• Screen Flows: Perfect for admins to create guided user experiences without writing code.
• Record-Triggered Flows: Commonly used by admins to automate record changes and business processes.
• Schedule-Triggered Flows: Slightly more technical, ideal for developers to handle batch processes and maintenance tasks.
• Platform-Event Triggered Flows: Highly technical, best managed by developers for real-time integrations and complex event handling.
• Autolaunched Flows: Flexible and powerful, suitable for both admins and developers depending on complexity.
• Best Practices for Collaboration: Learn how admins and developers can work together to leverage the strengths of both declarative and programmatic approaches. We’ll share tips on when to use Flow Builder versus Apex code to ensure your automations are efficient and maintainable.
• Testing and Maintenance: We’ll highlight the importance of testing flows and how developers typically handle testing in sandbox environments, while admins can focus on maintaining and optimizing flows in production.

Source: Salesforce Ben