Winter '27 (generally available 12 October 2026) returns completion actions to Marketing Cloud Next as a core capability. Per the release note, marketers no longer need a dedicated flow to notify a user, send an autoresponder email, or assign a lead. Anyone who came from Marketing Cloud Account Engagement will recognise the pattern: a small, named action attached to the thing that triggered it, instead of a flow that exists only to do one job.

Product

Marketing Cloud Next

Edition

edition not stated in the source

Topic

Flow for marketers

Confidence

Medium - shown in a credible source

Last verified

26 September 2026

Who this applies to

• Marketing Cloud Next teams that built flows purely to send a confirmation, alert a person or route a lead
• Edition: not stated in the release note summary we checked
• Winter '27 orgs from 12 October 2026

Why it matters

Single-purpose flows are the ones nobody documents. Six months in, a form has three flows attached, two of them do the same thing, and the person who built them has moved on. Completion actions put the behaviour where the next marketer will look for it, and they cut the number of flows an admin has to keep running.

Try it

1. Before the release: list every active flow in the marketing app whose only job is to notify someone, send one autoresponder, or assign a lead. Note what triggers each one.
2. For each, decide whether it is a candidate. A flow that also updates fields, waits, or branches stays a flow.
3. After 12 October, in a sandbox if you have one: rebuild one candidate as a completion action on its trigger and run the trigger end to end.
4. Deactivate the old flow only after the completion action has fired correctly in production for a real submission. Keep the flow inactive, not deleted, for a cycle.
5. Update whatever runbook or list you keep of marketing automations so the action is discoverable.

Example use case

An events team has a webinar registration form with a flow that emails a confirmation and a second flow that alerts the field marketer for enterprise sign-ups. Both become completion actions on the form: autoresponder to the registrant, notification to the marketer. The team keeps the one real flow that adds the registrant to the reminder journey, and the automation list drops from three items to one.

Prerequisites, limitations and risks

• Winter '27 in your org (GA 12 October 2026)
• The release note summary names three actions: notify a user, send an autoresponder email, assign a lead. Do not assume other action types exist until you see them in your org
• Sandboxes for Marketing Cloud Next can consume credits for Data 360, messaging and Personalization. Keep the test small
• Edition and permission requirements are not stated in our source; confirm after upgrade

Documented behaviour above comes from the sources listed below. Availability varies by edition, SKU and region - confirm entitlements in your own org before you rely on a feature.

Sources

• Marketing Completion Actions (Winter '27 release notes) Salesforce Help, 18 August 2026
• Winter '27 marketing release notes Salesforce Help, 18 August 2026