Top 6 Types of Salesforce Flows Every Admin Should Master

Written By Gary Elbaum

Automation inside Salesforce is now centered on Flow. Process Builder and Workflow Rules are legacy tools. Modern orgs rely on Flow for everything from background automation to guided user experiences. Below are the six primary Flow types every admin should understand and use strategically.

1. Record-Triggered Flow

Most commonly used Flow type.

A Record-Triggered Flow runs automatically when a record is created, updated, or deleted. It replaces most Workflow Rules and Process Builder automations.

Two key modes:

  • Before Save – Fast field updates. Best for updating fields on the same record.

  • After Save – Used when creating related records, sending emails, calling subflows, or making callouts.

Use cases:

  • Auto-populate fields

  • Create follow-up Tasks

  • Update related records

  • Enforce business logic

  • Trigger notifications

Why it matters: This is the backbone of modern Salesforce automation. Performance is best when logic is consolidated into fewer flows per object.

2. Autolaunched Flow

Background automation without user interaction.

An Autolaunched Flow runs without screens. It can be triggered by:

  • Apex

  • Another Flow (Subflow)

  • REST API

  • Platform Event

  • Scheduled Path (via Record-Triggered Flow)

Use cases:

  • Reusable logic components

  • Complex calculations

  • Integration logic

  • Batch-style record processing

  • Utility flows called by other flows

Why it matters: Think modular architecture. Instead of building massive Record-Triggered Flows, extract logic into Autolaunched Subflows. This improves maintainability and reduces technical debt.

3. Screen Flow

Interactive user experience.

A Screen Flow presents screens to users in Lightning pages, utility bars, Experience Cloud, or Quick Actions.

It collects input, guides decisions, and performs actions.

Use cases:

  • Guided data entry

  • Quote or onboarding wizards

  • Conditional questionnaires

  • Multi-step approval intake

  • Admin tools for bulk updates

Why it matters: Screen Flows replace custom Visualforce and many lightweight LWC builds. For admins managing Salesforce without heavy development, this is a powerful no-code UI builder.

4. Scheduled Flow

Time-based batch automation.

A Scheduled Flow runs at a specific date/time and processes records in bulk. It behaves similarly to a batch job.

Unlike Scheduled Paths (inside Record-Triggered Flow), this type runs independently of a record change event.

Use cases:

  • Nightly cleanups

  • Subscription renewals

  • Stale opportunity reminders

  • Annual account reviews

  • Mass recalculations

Why it matters: Ideal for periodic processing when logic is not tied to a specific record update event.

5. Platform Event-Triggered Flow

Event-driven architecture.

This Flow runs when a Platform Event is received. Platform Events are part of Salesforce’s event bus system.

They allow decoupled communication between systems or internal processes.

Use cases:

  • Integration listeners

  • Real-time external system updates

  • Asynchronous processing

  • Complex orchestration patterns

Why it matters: Enables scalable integrations and modern architecture without heavy Apex.

6. Subflow (Reusable Flow Component)

Technically not a separate Flow type in creation, but functionally distinct in architecture.

A Subflow is an Autolaunched Flow designed to be called by other flows.

Use cases:

  • Centralized validation logic

  • Shared record creation logic

  • Reusable email notification engine

  • Multi-object update patterns

Why it matters: Encourages clean design. Reduces duplicate logic. Makes deployments safer and easier to test.

Strategic Comparison

  • Record-Triggered Flow

    • User Interaction: No

    • Trigger: Record create, update, or delete

    • Best For: Core object automation and business logic

  • Autolaunched Flow

    • User Interaction: No

    • Trigger: Apex, API, Subflow, Platform Event

    • Best For: Modular background logic and reusable processes

  • Screen Flow

    • User Interaction: Yes

    • Trigger: User action (button, Lightning page, utility bar, Experience Cloud)

    • Best For: Guided user experiences and data entry wizards

  • Scheduled Flow

    • User Interaction: No

    • Trigger: Time-based schedule

    • Best For: Batch processing and periodic automation

  • Platform Event-Triggered Flow

    • User Interaction: No

    • Trigger: Platform Event received

    • Best For: Event-driven integrations and asynchronous processing

  • Subflow

    • User Interaction: No

    • Trigger: Called by another Flow

    • Best For: Reusable logic and clean automation architecture

Architectural Guidance

For admins managing Salesforce in growing environments:

  1. Use Before Save Record-Triggered Flows for simple field updates.

  2. Use After Save only when needed.

  3. Move complex logic into Autolaunched Subflows.

  4. Use Scheduled Flows for bulk periodic work.

  5. Use Screen Flows to reduce custom development.

  6. Avoid stacking multiple Record-Triggered Flows on the same object when possible.

Final Perspective

Flow is now the primary automation engine in Salesforce. Mastery of these six types enables:

  • Cleaner automation architecture

  • Better system performance

  • Easier troubleshooting

  • Scalable design

  • Reduced technical debt

Admins who structure flows strategically — modular, documented, and performance-aware — move from reactive troubleshooting to intentional system design.

In modern orgs, Flow knowledge is no longer optional. It is core infrastructure.

Written w help of gpt

Gary Elbaum
Next

What is Salesforce CPQ