Emit Event Native Action

the emit event native action enables the emission of events that can trigger other playbooks through flow event triggers the emit event action sends events with specific data properties that are passed to the flow event trigger for use in the triggered playbook this allows actions in one playbook to dynamically trigger actions in another playbook overview the emit event action requires two inputs sensorname the name of the flow event sensor to emit (required) this must match an existing flow event sensor eventdata the data object to include in the emitted event (required) the structure of this data should match the schema defined for the flow event when the action executes successfully, it publishes a sensorevent with type flow and action emit , which can be received by flow event triggers in other playbooks the action uses an "at most once" execution guarantee to prevent duplicate event emissions turbine limits event chaining (event > playbook > emit event > playbook) to 10 levels by default adding and configuring the emit event native action drag and drop the emit event native action from the native action panel into the playbook click on the emit event action to open its configuration panel in the info section title provide a unique and descriptive title for the action (for example "emit event") key ensure the key is auto generated or manually configured to match the naming conventions (alphanumeric and underscores only) description (optional) add a description for clarity about the action's purpose click the configure button under the flow event data section in the select event to emit configuration screen existing flow event choose from previously created flow events select the event from the dropdown list create flow event if no relevant event exists, create a new one by selecting the create flow event tab for a new event flow event title provide a unique title for the event description add a detailed description of what the event does 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 add as many properties as required to structure the emitted data for downstream actions or flows once all properties are defined, click apply to save the event data configuration how emit event works when the emit event action executes validation the action validates that the sensorname is provided (action fails if missing) the sensor exists in the system (action fails if sensor not found) event creation if validation passes, the action creates a sensorevent with event type flow action emit event data the eventdata object you configured event schema the schema defined for the flow event sensor event publishing the event is published via the messaging system and can be received by flow event triggers in other playbooks result on successful execution, the action returns an emittedeventid in the result, which uniquely identifies the emitted event accessing event data in triggered playbooks when a flow event trigger receives an event emitted by the emit event action, the event data is accessible through the $event data prefix in expressions for example $event data propertyname accesses a property from the emitted event data $event data nestedobject property accesses nested properties $event data arrayproperty\[0] accesses array elements troubleshooting action fails with "sensorname is required" ensure you have selected or created a flow event sensor in the configuration the sensor name must be provided action fails with "sensor \[name] not found" the specified sensor does not exist verify that the flow event sensor exists in your system the sensor name is spelled correctly the sensor hasn't been deleted or renamed event not triggering other playbooks verify that the flow event trigger in the target playbook is configured to listen for the correct sensor name the playbook with the flow event trigger is active and enabled the event data structure matches what the triggered playbook expects event data not available ensure the event data properties are correctly configured and match the schema defined for the flow event sensor best practices use descriptive sensor names choose clear, descriptive names for your flow event sensors to make it easier to identify which events trigger which playbooks match event data schema ensure the eventdata structure matches the schema defined for the flow event sensor to avoid data access issues in triggered playbooks document event contracts document the expected event data structure and properties so other orchestrators know what data to expect when configuring flow event triggers test event flow test the event emission and reception flow between playbooks to ensure data is passed correctly before deploying to production handle event failures consider adding error handling or conditional logic around emit event actions to handle cases where the sensor might not exist or the event fails to emit