Flow Fundamentals for Marketing Cloud Next Users

First, the terminology, since it's easy to mix up:

• Agentforce Marketing is Salesforce's new name for its overall marketing product line (the rebrand of what used to be called Salesforce Marketing Cloud). It's the top-level umbrella, and it includes:
  • Marketing Cloud Account Engagement (MCAE) - formerly known as Pardot
  • Marketing Cloud Engagement (MCE) - formerly known simply as "Marketing Cloud," home of Journey Builder and languages like AMPscript/SSJS
  • Marketing Cloud Next (MCN) - a newer generation of natively-built, agentic marketing products (including Flow, Agentforce Campaign Creation, and Segment Intelligence), rather than a single standalone product
• Agentforce (no "Marketing" suffix) refers to Salesforce's AI agent technology, which is also available inside Marketing Cloud Next as a way to build campaigns and flows using natural-language prompts.

This article is specifically about Flow Builder inside Marketing Cloud Next. Where relevant, we'll call out how it compares to what you may know from Marketing Cloud Engagement or Marketing Cloud Account Engagement.

Note: this is a relatively new rebrand, so terminology across Salesforce's own materials is still settling - double-check current naming before publishing if this article will be live for a while.

Flow Builder is Salesforce's drag-and-drop visual interface for automating processes. Instead of manually repeating a task, you tell the system what you want to happen, in what order, and which assets are involved - then Flow Builder turns that into a working automation.

In Marketing Cloud Next, Flow Builder is the automation engine behind everything: emails, SMS, forms, and what happens after someone interacts with any of them. If you send a message or publish a form, a flow determines what happens next.

Every flow orchestrates three core assets:

• Segment / Audience - who the flow applies to
• Content - emails, SMS, WhatsApp messages, forms, landing pages, website visits
• Actions - what happens, in what order, and on what timing

Historically, yes - Flow Builder was primarily a Salesforce admin tool used for back-end workflows, screen flows, and kicking off Apex or API calls. Marketing Cloud Next uses the same Flow Builder, but marketing-specific flows are often called marketing flows or citizen flows in Salesforce documentation. Both terms refer to the same thing.

Giving marketers access to flow doesn't mean giving them full admin-level access. Salesforce provides out-of-the-box permission sets that fine-tune exactly which flow elements a marketer can use - and admins can build custom permission sets for even more granular control. So marketing teams get flow access without losing back-end governance.

• Send communications across email, SMS, WhatsApp, and mobile push
• Wait for engagement, a set amount of time, or a specific event
• Update records - not just leads and contacts, but any CRM object you have permission to touch
• Branch with decisions - route people down different paths based on engagement, criteria, or subscription status
• Optimise with Path Experiment - build multiple paths, compare performance, and auto-select a winner (e.g., testing email vs. SMS engagement)

There are hundreds of flow types available in Salesforce generally, but marketers mainly work with a handful:

1. Automation Event (Event-Triggered) Flows

Triggered by an action - a form fill, an email click, a subscription, or a custom event (e.g., a visit to a pricing page). These run in the background once activated and are commonly used to replace completion actions for teams migrating from Marketing Cloud Account Engagement (Pardot). They're also used to route leads and form submissions to the right team.

2. Segment-Triggered Flows

Triggered when you pull a segment using Data 360/Data Cloud. Anyone in that segment runs through the flow. You can add exit rules and end steps to exclude certain people (e.g., partners or competitors). Segment-triggered flows can run:

• Once - for a single send with a defined start/end time and time zone
• Recurring - on a repeat schedule (hourly to yearly), useful for nurtures or journeys where new people should keep entering over time

3. Data Cloud (Data 360) Flows

Require Data Cloud permissions and run based on Data 360 information - for example, converting a prospect and alerting sales once someone crosses an engagement score threshold.

4. CRM Record-Triggered Flows

A newer flow type triggered when a lead or contact record changes (e.g., a lead moves to a new lifecycle stage), enabling automation based directly on CRM record changes.

5. Auto-Launched Flows

Run in the background and are triggered by other flows, Apex, or REST API - effectively reusable subflows that wait to be called by another process.

1. Agentforce (AI-assisted build) - Use natural-language prompts to have Agentforce draft a campaign brief and build the flow for you (including messages and wait steps). You can also upload a campaign brief document and have Agentforce build a flow grounded in that file. This method is best for simple, linear nurtures and is a strong starting point for beginners - you can always refine it further in Flow Builder.
    
2. Campaign Canvas - Inside a campaign, choose a flow type (single email, automation event, segment-triggered) and build the basic structure - wait steps, additional emails, WhatsApp messages - without ever opening Flow Builder directly.
    
3. Flow Builder (direct build) - The full visual builder, best for advanced flows: decision splits, Path Experiments, nurtures/journeys, and anything requiring exit rules (which can only be configured here).

A common workflow: build the base structure using Agentforce or Campaign Canvas, then fine-tune it in Flow Builder before activating.

• Canvas - where you build the flow visually
• Toolbox - your available resources and elements
• Errors/Warnings panel - a checklist of what must be fixed before activation
• Connectors (+ icons) - click to insert a new element between steps
• Elements - the building blocks of a flow, colour-coded by type:
  • Interaction elements (e.g., send an email, create a consent record, trigger a subflow)
  • Logic elements (decisions, Path Experiments, wait steps) - shown in orange/yellow
  • Data elements (get records, create records, update records) - shown in pink

• Event-triggered flows fire off a selected event (email engagement, form fill, subscription, or a custom event you define).
• Segment-triggered flows are configured with a Data 360 segment and a run schedule. For recurring flows, you can set the segment to refresh immediately before every run - this is generally recommended over a fixed refresh schedule, since refreshing in both places can waste credits, and refreshing within the flow guarantees the most current data every time it runs.

Debug mode lets you test a flow against selected records and route test sends to chosen destinations. Keep "run automation in rollback mode" enabled during testing - this undoes the actions so no real data changes are saved. Always debug flows that update records or contain decision splits.

Versioning lets you save a flow as a new version rather than overwriting it, so you can roll back if something breaks, or build a new version while the current one stays live. Add notes to each version so others can see what changed.

Pausing is currently supported for segment-triggered flows (support for form- and event-triggered flows is coming). Paused flows are still considered active but won't send. Note: wait-step timers keep counting down even while a flow is paused - they don't freeze. So if someone is partway through a wait step when you pause, and you keep the flow paused past the original wait duration, they'll move straight to the next step as soon as you reactivate the flow, without waiting again.

Marketing Cloud Next ships with 300+ flow templates, including six built specifically for marketing use cases (searchable by "marketing" in the template list). Templates let teams start from a working foundation instead of a blank canvas - and any flow you build can be saved as a reusable template for your own team.

Important: saving an existing flow as a template does not create a separate copy - it converts it. If you delete the resulting template, the original flow's build is gone too, and flows do not go to a recycle bin. Duplicate first if you want to preserve the original.

A widely recommended starter template is "Upsert a Record for a Person" - it checks whether a contact or lead already exists, updates it if so, and creates a new record (lead, contact, or CRM prospect) if not. Built once as a subflow, it can be called from any form-triggered flow.

• Form-triggered flow with auto-responder - calls an upsert subflow, checks a marketing opt-in checkbox, creates a consent record if opted in, and sends a transactional auto-responder email immediately (using the form submission itself as the data source, so you don't have to wait ~24 hours for the record to sync to Data Cloud).
• Message series flow - sends an email, waits up to a set number of days for a click, and if there's no engagement, follows up via a different channel (e.g., SMS) - useful for testing which channel drives better engagement per audience.
• Prospect auto-convert - when someone crosses an engagement threshold, the flow creates a lead and alerts sales with a summary of the person's activity.
• Custom event–triggered flow - for example, triggering on a pricing-page visit to create a lead and a sales follow-up task.