Notifications

Notifications are for work nobody is watching. A schedule or a Flow's notify step says who hears about what.

What can be sent

A schedule names the outcomes it reports: When a run fails, When a run finishes with warnings, When a run succeeds and When a run is cancelled. A Flow's notify step sends when its wires say. A run you start yourself reports on the screen you are watching instead.

A notification about a failure says which node failed and what it hit, in the node's name as it appears on the canvas.

Who receives them

• People. Name any account. The message goes to the email address on the account when it is sent, so a changed address follows the person.
• Destinations. An administrator creates named destinations in Settings → Notifications: an email address list, a Slack channel or a Discord channel. A Slack or Discord webhook address is itself a credential, so it lives in a destination and never in a pipeline or a Flow. Each destination has an access list deciding who may send to it.

When you edit someone else's schedule, only the recipients you add are checked against your access; the ones already there stay, even ones you cannot see.

Setting it up

Email needs the mail relay, set once in Settings → Notifications. Slack and Discord need only a destination. Trinium's own alerts about itself go to the destinations named in Send instance alerts to.