14.2 Data Cloud-Triggered Flows & Real-Time Business Orchestration

14.2 Data Cloud-Triggered Flows & Real-Time Business Orchestration

Quick Answer: A Data Cloud-Triggered Flow is a specialized flow type in Salesforce Flow Builder that executes native declarative business logic inside Core Salesforce whenever data is created or updated within a Data Model Object (DMO) or Calculated Insight. Unlike traditional Record-Triggered Flows—which listen only to standard and custom Salesforce CRM objects (Account, Contact, CustomObject__c)—Data Cloud-Triggered Flows listen directly to Data Cloud canonical lakehouse objects (identified by the __dlm suffix, such as UnifiedIndividual__dlm or SalesOrder__dlm). They execute asynchronously in System Mode without sharing, allowing administrators to create Cases, assign Tasks, send Chatter/Slack notifications, or invoke external actions without writing custom code or provisioning integration middleware.

---

Architecture of Data Cloud-Triggered Flows

Salesforce Flow Builder provides a dedicated trigger category specifically designed to bridge Data Cloud's hyper-scale data engine with Core Salesforce CRM business processes.

+-------------------------------------------------------------------------------------------------+
|                           DATA CLOUD-TRIGGERED FLOW ARCHITECTURE                                |
+-------------------------------------------------------------------------------------------------+
|                                                                                                 |
|   DATA CLOUD LAYER (Hyperforce Lakehouse)                                                       |
|   ┌───────────────────────────┐      ┌───────────────────────────┐                              |
|   │ Ingestion & Transformations│ ───> │ Data Model Objects (DMOs) │                              |
|   │ (Stream & Batch Updates)  │      │ (e.g., SalesOrder__dlm)   │                              |
|   └───────────────────────────┘      └─────────────┬─────────────┘                              |
|                                                    │ Record Change / Upsert                     |
|   CORE SALESFORCE CRM LAYER                        ▼                                            |
|   ┌─────────────────────────────────────────────────────────────────────────────┐               |
|   │                   DATA CLOUD-TRIGGERED FLOW ENGINE                          │               |
|   │  - Object: SalesOrder__dlm                                                  │               |
|   │  - Trigger: A record is created or updated                                  │               |
|   │  - Condition: Status__c = 'Cancelled' AND TotalAmount__c > 1000             │               |
|   └──────────────────────────────────────┬──────────────────────────────────────┘               |
|                                          │ Asynchronous Execution (System Mode)                 |
|                                          ▼                                                      |
|   CORE CRM AUTOMATION ACTIONS                                                                   |
|   ┌────────────────────┐   ┌────────────────────┐   ┌────────────────────────┐                  |
|   │ Create Sev-1 Case  │   │ Assign High-Pri    │   │ Dispatch Slack Alert   │                  |
|   │ in Service Cloud   │   │ Task to AE         │   │ to Retention Swarm     │                  |
|   └────────────────────┘   └────────────────────┘   └────────────────────────┘                  |
+-------------------------------------------------------------------------------------------------+

How the Trigger Operates

1. Object Selection: When authoring the flow in Flow Builder, the administrator selects Data Cloud-Triggered Flow as the flow type. In the Object selector, the administrator chooses the triggering Data Model Object (DMO). Standard and custom DMOs are exposed with their full API names, appended with __dlm (e.g., DeviceApplicationEngagement__dlm, Case__dlm, UnifiedIndividual__dlm).
2. Trigger Evaluation: The flow can be configured to fire on:
   • A record is created: Fires when a net-new record is ingested and harmonized into the DMO.
   • A record is created or updated: Fires when new records arrive or existing harmonized records are modified by continuous data pipelines.
3. Entry Conditions & Filtering: To prevent run-away flow executions and conserve system resources, entry conditions must be tightly scoped using field conditions or custom formulas:
   • Condition Requirement: TotalAmount__c Greater Than 5000 AND PaymentStatus__c Equals 'Failed'.
   • When to Run the Flow for Updated Records: Options include Every time a record is updated and meets the condition requirements or Only when a record is updated to meet the condition requirements. Choosing "Only when updated to meet" acts as a state-change filter, firing only on the transition into the qualifying state.

---

Common Enterprise Use Cases

Data Cloud-Triggered Flows provide an immediate operational bridge between big data insights and front-office employee productivity.

+-------------------------------------------------------------------------------------------------+
|                            ENTERPRISE ORCHESTRATION USE CASES                                   |
+-------------------------------------------------------------------------------------------------+
|                                                                                                 |
|   1. REAL-TIME VIP ESCALATION         2. HIGH-INTENT AE OUTREACH        3. INSTANT REWARDS      |
|   ┌────────────────────────┐          ┌────────────────────────┐        ┌─────────────────────┐ |
|   │ DMO: Case__dlm         │          │ DMO: WebEngagement__dlm│        │ DMO: Order__dlm     │ |
|   │ Filter: Sentiment < 2  │          │ Filter: Pricing Page >3│        │ Filter: Spend >$500 │ |
|   │ AND Tier = 'Platinum'  │          │ AND Account != Null    │        │ Action: Credit 5000 │ |
|   │ Action: Create Sev-1   │          │ Action: Assign AE Task │        │ loyalty points &    │ |
|   │ Case & Alert Manager   │          │ & Send Slack alert     │        │ trigger SMS voucher │ |
|   └────────────────────────┘          └────────────────────────┘        └─────────────────────┘ |
+-------------------------------------------------------------------------------------------------+

Use Case 1: Real-Time High-Priority Case Creation for VIP Customers

• Business Scenario: A global luxury hospitality brand ingests guest survey responses and mobile app complaints into Data Cloud. When a high-tier guest submits a complaint, the company must open a high-priority service ticket in Service Cloud within 60 seconds.
• Implementation:
  • Triggering Object: CustomerFeedback__dlm (Custom Engagement DMO).
  • Entry Condition: Rating__c Less Than Or Equal 2 AND GuestTier__c Equals 'Diamond'.
  • Flow Action: Invokes a Create Records element to insert a new Case record in Service Cloud, populating the AccountId, ContactId, priority (High), and routing it to the Executive Escalations Omni-Channel Queue.

Use Case 2: High-Intent Sales Lead Prioritization & AE Notification

• Business Scenario: A B2B SaaS enterprise tracks software trial usage and documentation browsing via the Data Cloud Web & Mobile SDK. When an enterprise account's technical evaluation team visits the enterprise pricing or API documentation pages more than 5 times in a single day, the account team must be alerted immediately.
• Implementation:
  • Triggering Object: DeviceApplicationEngagement__dlm.
  • Entry Condition: PageCategory__c Equals 'Enterprise_Pricing'.
  • Flow Action: The flow queries the Core CRM Account record matching the visitor's company domain, creates an urgent Task assigned to the Account Executive, and publishes a notification to the account's private Slack channel using the native Flow Slack integration.

Use Case 3: Real-Time Loyalty Point Calculation & Instant Reward Delivery

• Business Scenario: A multi-brand retail apparel chain ingests brick-and-mortar point-of-sale (POS) transactions. When a loyalty member completes an in-store transaction exceeding $250, the member should immediately receive bonus tier points and an SMS confirmation.
• Implementation:
  • Triggering Object: SalesOrder__dlm.
  • Entry Condition: GrandTotalAmount__c Greater Than Or Equal 250.00.
  • Flow Action: Updates the loyalty ledger custom object in Core CRM, recalculates tier status, and triggers a transactional SMS through Salesforce Digital Engagement.

---

Execution Context, Governance & Limits

Because Data Cloud processes petabytes of enterprise data across distributed infrastructure, Data Cloud-Triggered Flows operate under specific execution rules and governor limits.

+-------------------------------------------------------------------------------------------------+
|                            FLOW EXECUTION CONTEXT & GOVERNOR LIMITS                             |
+-------------------------------------------------------------------------------------------------+
|                                                                                                 |
|   EXECUTION CONTEXT                       GOVERNOR LIMITS & BULKIFICATION                       |
|   - System Mode Without Sharing           - Standard Flow SOQL query limit: 100 queries         |
|   - Ignores running user permissions      - Standard DML statement limit: 150 statements        |
|   - Automated process execution           - Maximum CPU time: 10,000 milliseconds               |
|   - Asynchronous queue handoff            - Bulkification: Processed in chunks of up to 200     |
|                                                                                                 |
|   IDEMPOTENCY SAFEGUARDS                  ANTI-RECURSION DESIGN                                 |
|   - DMO updates may fire in bursts        - Prevent circular updates between DMO & Core CRM     |
|   - Check existing records before insert  - Avoid firing DLO ingestion from CRM records that    |
|   - Use external ID matching for upserts    were created by Data Cloud-Triggered Flows          |
+-------------------------------------------------------------------------------------------------+

1. System Mode Execution

Data Cloud-Triggered Flows run strictly in System Mode Without Sharing:

• The flow executes under the permissions of an automated internal integration context, not the interactive end user who triggered the event in an external app.
• The flow can create, read, update, and delete Core CRM objects regardless of individual user Profile or Permission Set restrictions.
• Security Consideration: Administrators must carefully design Flow logic to ensure unauthorized record exposure or erroneous data modifications do not occur.

2. Asynchronous Execution & Bulkification

• Asynchronous Decoupling: Ingestion pipelines in Data Cloud do not wait for Flow execution to finish. Data Cloud writes records to the lakehouse and asynchronously places trigger notifications into the Core Salesforce processing queue.
• Bulkification: When batch data streams or high-volume streaming transforms write thousands of records to a DMO simultaneously, the Flow engine groups the records into bulkified batches (up to 200 records per execution batch).
• Governor Limit Adherence: Inside the Flow, administrators must observe standard Salesforce Flow best practices: never place SOQL queries (Get Records) or DML operations (Create Records, Update Records) inside Flow Loops. Place records into collections and perform a single DML operation outside the loop to avoid hitting the 100 SOQL / 150 DML governor limits.

3. Idempotency & Circular Loop Prevention

• In high-velocity data ingestion environments, multiple DMO records or updates can arrive within seconds. If a flow blindly inserts a new Task or Case on every DMO event without checking for existing open records, the CRM org will suffer from severe record duplication.
• Design Pattern: Always include a Get Records check at the beginning of the flow to verify whether an active Case or Task with matching external keys already exists before executing a Create Records element.
• Circular Trigger Recursion: If a Data Cloud-Triggered Flow creates a CRM Case, and that CRM Case object is mapped to a Data Cloud ingestion stream via the CRM Connector, the newly created Case could stream back into Data Cloud and trigger another DMO update. Architects must add filtering flags (e.g., Origin != 'DataCloud_Automated') to break circular ingestion-trigger loops.

---

Architectural Decision Matrix: Flow vs. Data Action vs. Batch Activation

To pass the Data Cloud Consultant exam, candidates must immediately recognize which automation mechanism matches a given architectural requirement.

---

Consultant Traps & Exam Scenarios

• Exam Trap: Attempting to use a Record-Triggered Flow on a DMO. In Flow Builder, selecting a standard "Record-Triggered Flow" will not expose Data Model Objects (__dlm). Record-Triggered Flows only listen to standard and custom Salesforce CRM objects. You must explicitly select the Data Cloud-Triggered Flow template.
• Exam Trap: Confusing Single-Org Flow with Cross-Org Orchestration. If a scenario requires Data Cloud to create records in a secondary, external Salesforce org (not the org hosting the Data Cloud instance), a local Data Cloud-Triggered Flow cannot touch the secondary org directly without custom callouts. The optimal architectural choice is a Data Action publishing a Platform Event to the secondary org via the Salesforce-to-Salesforce event bus, or a Webhook to MuleSoft.
• Exam Trap: Forgetting Bulkification in DMO Flows. When streaming transforms flush micro-batches into a DMO, flows execute on collections. If a candidate designs a flow with individual SOQL/DML elements inside a loop, the flow will fail due to governor limit exceptions. Always use collection operators.