Output
Notify
Raises an alert with a severity — into the run's own log and preview, and optionally by email or to a Slack, Teams or other chat webhook — then passes the rows on.
When to use it
Use it on a branch that should get attention, such as rows quarantined by Quality Rules or a failed run's log.
In a pipeline
Quality Rules / AssertionsNotify
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| Message | text | Yes | {count} rows were quarantined |
| Severity | select | — | warning |
| Also send | select | — | log |
| Email to | text | — | ops@example.com |
| Webhook address | password | — | https://hooks.slack.com/… |
| Only when rows arrive | checkbox | — | true |
Example
Alert when rows are quarantined
- Message={count} rows were quarantined
- Severity=Warning
| Order | Quality Reason |
|---|---|
| A-1043 | Amount is blank |
| Order | Quality Reason |
|---|---|
| A-1043 | Amount is blank |
Worth knowing
- With Only when rows arrive ticked (the default), an empty branch stays quiet.
- The alert always appears in the run log and in a Logging node's report; email (from your account in Account ▸ Email) and webhooks are extra.
- Previews show the alert but never send it.