Activate To Any Downstream System With Salesforce Data 360, High Scale Flow, and Mulesoft Connectors In Flow
Salesforce Data 360 (formerly known as Data Cloud) continues to evolve as the intelligent engine behind customer engagement. With the recent GA of Activation-Triggered Flows, the platform introduces one of its most powerful capabilities yet: the ability to automate outbound activation to any system the moment a Data 360 segment publishes or when a Data Model Object (DMO) is activated (using Batch DMO activation). This now allows you to automatically activate your customer data virtually either using a segment or DMO to any API-based system which isn’t limited to marketing, advertising, analytics, personalization, CRM, omni-channel journeys, or any other system or product of your choice.
Customer journeys today are non-linear and spread out across websites, applications, social channels, and in-person interactions — creating fragmented, ever-shifting engagement paths. As customers move unpredictably between touchpoints, businesses rely on multiple engagement platforms to keep up, but this often leaves data siloed across systems, making unified activation and orchestration increasingly challenging.
This feature closes the final gap between data activation and system action, enabling organizations to bridge insight with engagement — natively, securely, and without writing custom code.
Why Do Activation-Triggered Flows Matter?
Traditionally, segment and DMO activation in CDPs and integrations to external systems often required custom code, dedicated integration teams, middleware mapping, or manual coordination. Activation-Triggered Flows solve this by triggering a Flow automatically when a segment or DMO activation runs.
How Do Activation-Triggered Flows Work?
Activation-Triggered Flows connect Data 360, Flow, and external systems using a simple model:
- Activation Target – Defines where the segment audience / DMO records will be delivered.
- Activation Setup – You select Data 360 attributes to be activated, link either a segment or a DMO, activation target, and data space.
- Activation-Triggered Flow – Inside Flow Builder, you configure the Data 360 activation as the start node and define all downstream actions — writing to CRM, calling APIs, using MuleSoft connectors, or orchestrating automation chains.
Expanding Activation Power With MuleSoft Integration Connectors:
With MuleSoft for Flow integration connectors, Data 360 segments or DMOs can be activated virtually into any system — Marketo, HubSpot, NetSuite, ERP platforms, customer success systems, or custom APIs with no code required.
Sample Use Case: Win-Back Audience → External System → Sales Follow-Up
A Win-Back Account segment based on churn risk or lapsed usage publishes:
- Activation-Triggered Flow processes the activation.
- Flow pushes the audience into Marketo or HubSpot via MuleSoft.
- CRM updates occur based on engagement.
- Sales automatically get tasks for follow-up.
Architecture Options:
Option 1 — Platform Named Credentials + External Service (Create HTTP callouts)
Use for simple REST integrations, lightweight API calls, and internal Salesforce applications or external systems.
Option 2 — MuleSoft Integration Connectors in Flow
Use for structured connectors, enterprise APIs, and multi-endpoint orchestration.
Steps to perform in an Activation-Triggered Flow:
Solution in runtime:
Conclusion:
Activation-Triggered Flows elevate Data 360 from a data platform to an activation platform. Any segment can now be delivered to any API, connector, or external system – Salesforce or not – with clicks, not code, and all at massive scale. With this capability, teams can operationalize insights, personalize experiences, automate journeys, drive cross-channel engagement, and activate data across their entire ecosystem – including homegrown applications – without custom code or integration overhead.
Want to see it in action?
Check out this quick demo showcasing how Activation-Triggered Flows work end-to-end and how easily you can activate any segment to any system with clicks, not code.
Help Documents
- Create an Activation for a Data 360 Target
- Create an Activation-Triggered Flow
- Mulesoft connectors in Flow
- Connecting to an API Without a Connector Using HTTP Callout
- Register an External Service
Written by
