With platform event–triggered flows, you can do all your automation in one place. Users can trigger a Flow when a platform event message is received. Unlike Process Builder, users can access all available records when a Flow is invoked by the platform event message. Previously, platform event–driven automation required you to use Process Builder and Flow Builder.
Platform event-triggered flow launches when a platform event message is received. This Auto launched flow runs in the background.
What is Platform Event ?
Platform Event is based on Event-Driven Architecture which enable apps to communicate inside and outside of Salesforce. Platform events are based on the publish/subscribe model and work directly with a message bus which handles the queue of incoming events and processes listening for them. This is built in real time integration patterns in the Salesforce Platform which helps to reduce point-to-point integration.
Learn more here about platform event.
In this session we will talk about why we should use Platform Event Trigger flow and how to create platform event flow in Salesforce.
Platform Event Considerations
- If platform event–triggered flows, paused flow interviews, and processes are subscribed to the same platform event, we can’t guarantee which one processes each event message first
- A flow can receive a batch of event messages at once, up to a maximum of 2,000 event messages
- Debug logs for platform event–triggered flows and resumed flow interviews appear under the Automated Process user
Yeah! You know the way to go with that Platform Event-Triggered Flow now. Read more blogs and find out about other flow types too.