Send Notification Native Action

the send notification native action enables you to send actionable email alerts to users and groups notifications can include contextual data and provide rich redirection options to help users take immediate action overview the send notification action allows playbook authors to send email alerts to specific users or groups include dynamic content using playbook properties and expressions provide clickable links to records, reports, dashboards, or playbooks deliver notifications via email based on user email frequency preferences key benefits native action integrated directly into the playbook builder for streamlined workflow creation flexible recipients send to individual users, user groups, or dynamically reference recipients using expressions dynamic content use playbook properties and expressions to inject contextual information into notification titles and bodies click targets provide direct links to relevant content (records, reports, dashboards, playbooks) in email notifications for immediate action email delivery notifications are automatically sent via email based on user email frequency preferences (default every 30 minutes) inputs the send notification action requires the following inputs required inputs title the notification title/header text displayed in the notification can be plain text or include playbook properties/expressions example "security alert ${$event data threattype}" recipients the users or groups who will receive the notification can be selected from dropdown (users or groups) can reference playbook properties (e g , $actions createrecordname result assigned to ) can use expressions to dynamically determine recipients supports multiple recipients (array of user/group objects or email addresses) recipient format user/group objects { id "userid", type "user", name "john doe" } email addresses string values (e g , "user\@example com" ) playbook properties reference to upstream action outputs body the notification message content can be plain text or include playbook properties/expressions supports multi line text example "record ${$actions createrecordname result tracking id} has been created and assigned to ${$actions createrecordname result assigned to}" optional inputs click target type the type of target to open when the notification is clicked options "record" , "report" , "dashboard" , "playbook" if not specified, notification has no click target click target id the identifier of the target to open format depends on the click target type (see click targets section below) can reference playbook properties or use expressions configuring the send notification action step 1 basic configuration open your playbook in the turbine canvas from the add panel, drag and drop the send notification action into your canvas click on the action block to configure it provide a unique title and key for the action title the display name for the action (e g , "notify security team") key a system generated unique identifier (editable but must follow naming conventions) description (optional) internal note to describe the purpose of the action step 2 configure notification details notification title enter the header text for your notification use the ➕ icon to inject playbook properties or build expressions example "security alert ${$event data threattype}" notification recipients click to open the recipient selector select users or groups from the dropdown, or use the ➕ icon to inject a playbook property or expression you can add multiple recipients recipients can be specific users (selected from dropdown) user groups (selected from dropdown) dynamic references (e g , $actions createrecordname result assigned to ) email addresses (when using expressions) notification body compose your message using plain text use the ➕ icon to inject playbook properties or build expressions supports multi line text example "record ${$actions createrecordname result tracking id} has been created " example dynamic parameters ${$event data recordid} access event data ${$actions actionname result tracking id} access action outputs ${$variables variablename} access playbook variables ${$inputs inputname} access playbook inputs step 3 configure click target (optional) the click target setting defines where users will be redirected when they click on a link in the email notification this provides contextual access to relevant content within turbine and allows users to take immediate action target type select one of the following options application record ( "record" ) report ( "report" ) dashboard ( "dashboard" ) playbook ( "playbook" ) target id configure based on the selected target type application record redirects users to a specific record within a selected application configuration target type select application record application use the dropdown to select the target application tracking id provide the record's tracking id (not the internal record id) manual entry type the tracking id playbook property use the ➕ icon to insert a property (e g , $actions createrecordname result tracking id ) expression build a dynamic expression note the action automatically resolves tracking ids to record ids the format stored is "appid/recordid" , but you provide the tracking id report redirects users to a specific report view for quick data analysis or review configuration target type select report application select the application that houses the report report choose a report from the filtered list associated with the selected application use case ideal for summarizing events or redirecting users to reporting dashboards built on historical data dashboard sends users to a specific dynamic dashboard when the notification is clicked configuration target type select dashboard workspace select the workspace containing the dashboard dashboard use the dropdown to choose the destination dashboard use case use when visual analysis is required the dashboard should be shared with the recipients or they must have view access permissions tip pair this with dashboard level or runtime filters to offer a more tailored view of the data upon redirect playbook launches or redirects the user to a specific playbook in turbine configuration target type select playbook playbook select the target playbook from the dropdown use case ideal for triggering manual actions, workflows, or enabling users to resume paused automation step 4 apply changes click apply to save your configuration and include the action in your automation flow outputs the send notification action provides the following outputs success output when the notification is sent successfully, the action completes with status success result "notificationsent" note the send notification action is a fire and forget operation it does not return detailed output data the action succeeds if the notification is queued for delivery error output if the notification fails to send, the action returns error error information containing details about why the notification failed common error scenarios invalid recipient ids or email addresses recipients not found or not accessible invalid click target configuration missing required inputs (title, recipients, body) feature not enabled (usernotifications feature must be enabled) how notifications are delivered notifications are delivered via email based on user email frequency preferences default email frequency every 30 minutes (configurable per user) users can configure their email notification preferences in their user settings email notifications include the notification title and body, with links to the click target (if configured) click targets in email notifications allow recipients to navigate directly to relevant content (records, reports, dashboards, or playbooks) use cases example 1 notify on record creation scenario send a notification to the assigned user when a new record is created configuration title "new record created ${$actions createrecordname result tracking id}" recipients $actions createrecordname result assigned to body "a new record has been created and assigned to you please review and take action " click target type "record" click target id "${$actions createrecordname result application id}/${$actions createrecordname result tracking id}" result the assigned user receives a notification with a direct link to the new record example 2 security alert notification scenario notify the security team when a high severity threat is detected configuration title "security alert ${$event data threattype}" recipients select "security team" group from dropdown body "a ${$event data severity} severity threat has been detected ${$event data description} please investigate immediately " click target type "record" click target id "${$event data applicationid}/${$event data recordtrackingid}" result the security team receives an immediate notification with context and a link to the threat record example 3 mssp incident collaboration scenario mssps can use the notification action to notify customers of active threats or policy violations remediation status updates scheduled or unscheduled service disruptions configuration title "incident update ${$variables incidentid}" recipients use expression to reference customer contact from record $actions getrecordname result customer contact body "your incident ${$variables incidentid} has been updated status ${$actions updaterecordname result status} please review the details " click target type "report" click target select customer facing incident report result customers receive timely updates via email, building trust and maintaining transparency example 4 dashboard alert scenario notify stakeholders when key metrics exceed thresholds configuration title "alert ${$variables metricname} threshold exceeded" recipients select "stakeholders" group body "the ${$variables metricname} has exceeded the threshold of ${$variables threshold} current value ${$variables currentvalue} review the dashboard for details " click target type "dashboard" click target select the metrics dashboard result stakeholders receive alerts with direct access to the relevant dashboard for analysis example 5 playbook completion notification scenario notify users when a playbook completes successfully configuration title "playbook completed ${$playbook name}" recipients use expression $inputs notifyrecipients body "the playbook '${$playbook name}' has completed successfully ${$actions finalactionname result summary}" click target type "playbook" click target select the completed playbook result users receive completion notifications with a link to review the playbook execution details best practices use dynamic recipients reference recipients from upstream actions or playbook inputs to make notifications flexible and reusable include context use playbook properties and expressions to include relevant context (record ids, status, values) in notification titles and bodies set click targets always configure click targets when possible to provide direct access to relevant content and improve user experience test recipients verify that recipient references resolve correctly, especially when using dynamic expressions keep titles concise notification titles should be brief and descriptive, as they appear as email subject lines use clear body text write notification bodies that clearly explain what happened and what action (if any) is required consider email frequency be aware that email notifications are batched based on user preferences (default every 30 minutes) for urgent notifications, consider using other communication channels validate click targets ensure click targets (especially record tracking ids) are valid and accessible to recipients troubleshooting email not received verify recipients are valid users or groups check that recipients have access to the tenant/account verify usernotifications feature is enabled check user email notification preferences (frequency settings) verify user email address is configured correctly check email delivery logs for errors remember emails are batched (default every 30 minutes) click target not working verify click target id format is correct for the target type for records, ensure tracking id is valid and record exists check that recipients have access to the target (application, report, dashboard, playbook) verify click target type matches the target id format invalid recipients ensure recipient ids or email addresses are correct verify recipient references resolve to valid users/groups check that recipients exist in the tenant/account expression errors verify playbook property references are correct (e g , $actions actionname result property ) check that referenced actions have completed successfully ensure expression syntax is valid feature not enabled ensure usernotifications feature is enabled for your account contact support if you believe this feature should be available