Add an Email Notification¶
Add an Email notification action to a Flow to deliver alerts to Qualytics users, the members of Qualytics teams, and any other email address whenever the trigger activates. For delivery behavior and the concept behind the channel, see the Notifications deep dive.
Email Delivery
Notification emails are sent through the Email integration when one is connected, or otherwise through the email service configured for your deployment, when it has one. If neither is available, email notifications are not delivered.
Permission Required
To edit and publish a Flow, you need the Editor team permission on every datastore it relates to. Admins are exempt. See Flow Permissions for details.
Field reference¶
The Email Settings panel shows the following fields.
| Field | Required | Type | Description |
|---|---|---|---|
| Send to | List | Who receives the email, as one list of chips. Search to pick Qualytics users and teams (the Users and Teams tabs narrow the results), or type any email address and press Enter; several addresses separated by ; or , are added at once. A typed address that belongs to a Qualytics user becomes that user's chip. A malformed address is named under the field and is not added. Users show with their avatar and name, and teams show the avatars of their members. At least one recipient is required. |
|
| Email Subject | Text | The subject line of the notification email. It supports the same dynamic tokens as the message, and already comes filled in with the trigger's default subject. A subject is always sent on one line, so any line breaks its tokens produce are collapsed to spaces, and it is shortened to 150 characters with a trailing ... when it runs longer. Clear the field to fall back to the trigger's default. |
|
| Message | Text | The notification message, with dynamic tokens resolved when the Flow runs. It supports Markdown formatting, such as bold, lists, and links (see Message). It already comes filled in with the trigger's default template, and the action cannot be saved with it empty. |
Who receives the email
- Typed addresses always receive it.
- Picked users are reached at their current email address, so a user who changes address keeps receiving the Flow's emails.
- Picked teams are read when the email is sent, so a member who joins later receives it too.
- A person who is both picked and in a picked team, or whose address is also typed, receives one email.
- Picked people receive the email only if they could see the data it is about: Admins, and the members of the teams assigned to the event's datastore. An email after an operation action is judged on that operation's datastore. An email with no datastore behind it, such as one from a Schedule or Manual Flow that runs no operation first, reaches every team member. Anyone else is skipped, and the action's result names them, for example
skipped 1 person without access to this data (Jane Doe). - A deactivated user stays in the list but is not emailed.
The panel warns about these cases before you publish. A user chip shows with the reason when that user will not be emailed (No access to a datastore, In no team, or Deactivated), and a team chip lists the members who will not be. Only users with an email address can be picked; service users can't.
Tip
Use the autocomplete feature (triggered by Ctrl+Space) to insert variables such as {{flow_name}}, {{container_name}}, and {{datastore_name}}. The autocomplete only suggests variables that are valid for the selected Flow trigger type.
Reset to defaults
The Reset to defaults button at the top of the settings panel restores the Message and the Email Subject to the trigger's defaults.
The default subject for each trigger
Each trigger opens the field on a subject written to name the outcome, so a scan's health is readable from the inbox without opening the mail.
| Trigger | Default Subject |
|---|---|
| Schedule | Scheduled run: {{flow_name}} |
| Operation Completed | {{operation_result}}: {{operation_type}} operation on {{datastore_name}} |
| Anomalous Table or File Detected | {{anomaly_count}} anomalies found in {{container_name}} ({{datastore_name}}) |
| Anomaly Detected | {{anomaly_type}} anomaly in {{container_name}} ({{datastore_name}}) |
| Anomaly Status Changed | Anomaly status changed to {{new_status}} in {{container_name}} |
| Manual | On-demand run: {{flow_name}} |
A notification chained after a Create Ticket action opens on Ticket {{ticket_number}} created, falling back to A ticket was created when there is no ticket number. One chained after an Update Ticket Status action opens on {{tickets_updated_count}} tickets updated, falling back to Tickets updated when there is no count.
If a subject ever renders to nothing at all, the email is sent as Qualytics Notification rather than with an empty subject line.
Steps¶
Step 1: Navigate to the Flows page by clicking Flows on the left side panel.
Step 2: On the Definitions tab, click the Flow. On its canvas, click the dashed Action placeholder after the trigger, or the + handle at the bottom edge of a node.
Step 3: In the List of Actions panel, pick the Notification category, then click Email. The Email Settings panel opens on the right-hand side.
Step 4: Fill in the fields. In Send to, search for users or teams and pick them, or type an email address and press Enter.
Step 5: Click Test Notification to send a sample message with dummy data and confirm the destination and formatting. A confirmation message appears when it is delivered.
Step 6: Click Save. The node shows a CHANGED badge and the You have unpublished changes banner appears on the canvas.
Step 7: Click Publish to make the action live.