You are here:
Trigger Flows with Data 360 Data
Run a flow automatically when a Data 360 record meets specified conditions.
Data Cloud-triggered flows start when a qualifying record changes in the object that you select in the Start element. A qualifying record is a new or changed record that meets the flow conditions. The object can be a DMO, a calculated insight object (CIO), or an accelerated external object.
Processes that load or process data can lead to a flow run, but they aren’t the trigger. These processes include data stream refreshes, source connectors, the Ingestion API, data transforms, and calculated insight jobs. A flow runs only when one of these processes produces a qualifying record.
You can use external objects created through Bring Your Own Lake (BYOL) to trigger an action. Accelerate the external objects before you use them in a flow or data action. If you select a DMO, the flow triggers only if you map the DMO as part of a data stream.
Flow Triggers
| Scenario | Can It Start a Flow? | What Actually Triggers the Flow |
|---|---|---|
| New or changed mapped DMO record | Yes | The record meets the start conditions. |
| Manual or scheduled data stream refresh | Sometimes | The refresh starts a flow only if it produces a qualifying new or changed mapped DMO record. The refresh itself isn’t the trigger. |
| Source connector or file ingestion | Sometimes | The data stream maps the source changes into qualifying DMO changes. |
| Ingestion API | Sometimes | The API loads data through a data stream and mapping. The API load produces a qualifying DMO change. |
| Batch data transform | Depends on configuration | The output DMO changes and meets the start conditions. The transform run alone doesn’t start the flow. Make sure to verify the supported output configuration. |
| New or changed CIO output record | Yes | The CIO output record changes and meets the start conditions. |
| Calculated insight job or Publish Now | Sometimes | The job starts a flow only if it produces a qualifying CIO output change. Job completion itself isn’t the trigger. |
| Accelerated BYOL external object | Yes | A qualifying record change is available after acceleration. |
| Non-accelerated BYOL external object | No | No supported trigger path exists. Accelerate the object first. |
| Refresh or re-ingestion that changes no records | No | No qualifying change exists. A successful refresh doesn’t mean that the records changed. |
| Flow activation or DMO mapping after records exist | No | Activating the flow or mapping a DMO doesn’t produce a qualifying change. Existing records don’t start the flow. |
| An update makes a record meet the start conditions | Yes, but only on a qualifying transition | The flow starts only if you select Only when a record is updated to meet the condition requirements in the Start element and an update changes a record from not meeting the start conditions to meeting them. Already-qualifying records don't trigger the flow. |
- Create a Data Cloud-Triggered Flow
Create a flow that starts when a qualifying record changes in a Data 360 object.
