Create a record-triggered flow to publish platform events of Data 360
actions. You can use the published platform event to resume your paused auto-launched flow. With a
record-triggered flow, you can update another record, send a notification, initiate a process, or
maintain data consistency. A record-triggered flow runs only when a record is created or updated.
It can update a record 10 times faster than a record-change process.
In the Quick Find box, enter Flows, and select
Flows.
Click New Flow.
Select Start From Scratch, then click Record-Triggered
Flow, and then click Create.
From the Object dropdown, select the Data Cloud action that you want to publish custom
events for.
Select A record is created or updated.
From the Condition Requirements dropdown, select All Conditions Are Met
(AND).
Define the condition. You can add more conditions as needed.
Select Only when a record is updated to meet the condition
requirements and Actions and Related Records.
Click Done.
On the canvas, click Add Element, and then click Create
Records.
Enter the label name and select Use separate resources, and literal
values.
From the Object dropdown, select the custom platform event that you want to publish.
Select a field, and set values for your custom platform event.
Click Done and then click Save.
Enter the flow label, click Save, and then click
Activate.
The record-triggered flow is triggered every time the record is updated and the conditions
are met.
When the flow is triggered, the custom platform event is published. Resume your paused
autolaunched flow with the published platform event.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.