Flow Event Trigger

the flow event trigger operates in conjunction with the emit event native action while the flow event trigger listens for and initiates a playbook based on emitted events, the emit event action generates those events within other playbooks adding and configuring the flow event trigger drag and drop flow event trigger to the playbook enter the title for the trigger in the flow event title field which will be used to identify the event in the playbook select either an existing flow event or a create flow event existing flow event choose from a list of already created flow events create flow event provide a flow event title enter a name for the event this is required to identify the flow event within the playbook the flow event name will be auto generated and used as a unique identifier add a description (optional) to explain the purpose of the event click configure to proceed to the next step in the event data section, define the properties for the event data to be emitted click add property to add a new data property property configuration string enter a text value or map to an existing property number define a numeric value the default is 0 , but you can configure it as needed boolean toggle between true or false using the provided options object add nested properties by clicking add property within the object array add an array of values by selecting add array item , and define the type of values it should include attachment select a property to include attachments, such as files or documents for more information about emit event native action, see emit event native action docid\ ygjjegmfw4bldailc pg documentation correlation between flow event trigger and emit event native action the flow event trigger and emit event native action work together as follows emit event native action generates events during the execution of a playbook sends event data, such as parameters and results, to the flow event trigger flow event trigger listens for events emitted by the emit event action initiates the corresponding flow upon receiving the event key considerations ensure that the flow event title matches exactly in both the emit event action and the flow event trigger event data defined in the emit event action is available for use in the playbook triggered by the flow event trigger the event(s) emitted and the playbook flow(s) it triggers are processed concurrently and distributed across a scaled service, along with the playbook emitting the event is not blocked from continuing execution of the next action, so there is no guarantee of order example scenario processing emails with event correlation emit event native action configured in a playbook to emit an event after processing emails includes data such as email sender, subject, and content flow event trigger listens for the emitted email event initiates a new playbook to save the email data into a database or trigger additional actions