Notification Actions

The Notification group builds a human-readable summary of what a run did, and delivers it by e-mail, Slack or Teams.

note

This group replaces the notifier half of the old Message Actions page. The e-mail actions moved to their own Email group, and the notifier no longer needs an e-mail client action — reports are rendered by the Aiviro Cloud.

The reporting pattern

1. Throughout the scenario, call Add Message whenever something noteworthy happens.
2. At the end, call Send As Email once to deliver the collected messages as a formatted report.

Messages accumulate in the Notifications panel, so you can see the report taking shape while you develop.

---

Add Message

Adds one entry to the notification queue.

📸 Screenshot needed — /img/editor/actions/notification/notifier_add.png

Capture: the Add Message form with Advanced options expanded so Title, Section ID and Section Title are visible, plus the Notifications panel with several messages of different types. Why it must be retaken: Title, Section ID and Section Title are new.

Parameter	Description
Message	Text to record. Accepts variables.
Type	Severity, which sets the colour in the report: INACTIVE (grey), SUCCESS (green), INFO (blue, default), WARNING (yellow), ERROR (red).
Title	Optional heading for this single message.
Section ID	Groups messages into a section of the report. Messages sharing an ID land in the same section. Optional.
Section Title	Heading shown for that section. Optional.

tip

Section ID turns a flat list into a structured report. In a loop over invoices, use the invoice number as the Section ID — every message about that invoice then appears together under its own heading.

Send As Email

Renders the collected messages into a report and sends it.

📸 Screenshot needed — /img/editor/actions/notification/notifier_send.png

Capture: two images — the Send As Email form with the Delivery selector showing both choices, and an example of the rendered report as it arrives in a mailbox. Why it must be retaken: the action no longer takes an e-mail client variable; Delivery and Language are new.

Parameter	Description
Recipients	Addresses separated by semicolons, e.g. a@example.com; b@example.com. Accepts variables.
Report Subject	Subject line. Default Aiviro Editor Report.
Language	Language the report is rendered in: cs, en, de or sk. Default cs. The report is always rendered by the Aiviro Cloud in this language, whichever delivery method you pick.
Delivery	Aiviro Cloud (default) also sends the e-mail server-side — nothing to configure. Email Account (SMTP) sends the cloud-rendered report through an Email Account from your Vault, so the mail leaves from your own domain.
Save report to logs	Also writes the rendered HTML and plain-text report into the log folder. Default on. Optional.

Send Slack Message

Posts a message to a Slack channel.

📸 Screenshot needed — /img/editor/actions/notification/slack_message.png

Capture: the Send Slack Message form. Mask: blur the token completely.

Parameter	Description
Slack Token	Bot or user OAuth token with the chat:write scope.
Channel ID	Target channel, e.g. C0123456789.
Message	Text to post.

Send Teams Message

Posts a message to a Microsoft Teams channel through an incoming webhook.

📸 Screenshot needed — /img/editor/actions/notification/teams_message.png

Capture: the Send Teams Message form. Mask: blur the webhook URL — it is a secret.

Parameter	Description
Webhook URL	Incoming-webhook URL of the Teams channel.
Message	JSON or plain-text content to post.

warning

The Slack token and the Teams webhook URL are credentials. Store them in the Vault and reference them as {{SECRET:KEY}} instead of typing them into the action — a project file with a live token in it should not be committed to Git.