25. Notifications & Slack

Notifications define who should be informed about important Klariton events. The settings page stores recipients, Slack webhook configuration, event toggles, newsletter opt-in, and billing email.

Current status: Notification settings are persisted. Email delivery and Slack pings may still be phased by environment. The app text explicitly marks some delivery behavior as phase 2.

Recipients

Under Settings -> Notifications, configure:

one or more email recipients,
optional Slack webhook URL,
newsletter opt-in,
separate billing email.

Slack webhook URLs must start with:

https://hooks.slack.com/

If you use Slack, make sure the workspace and channel are appropriate for the data you send there.

Event Categories

Notification events are grouped into:

Category	Examples
Content & Curation	New BIQs ready for review, translation done, generation failed, material processed or failed.
Billing & Account	Budget threshold, no payment method, trial ending, payment failed.
Engagement & Insights	First end-customer question, weekly summary, material gap.
Team & Organization	Member joined, role changed.
Agentic & Widget	First bot read, touchpoint error or widget offline.

For each event you can configure:

email on/off,
Slack on/off,
frequency: instant, daily, or weekly.

Slack event toggles become useful only after a valid webhook URL is set.

Test Slack

Use the test webhook action to validate webhook format. Depending on environment, this can be a format check rather than a real Slack delivery.

Billing Email

Billing email is separate from operational notification recipients. Use it for invoices and payment notifications. If left empty, Klariton falls back to the organization or owner address where configured.

Best Practices

Send billing events to finance or the owner.
Send content events to operators responsible for BIQ review.
Send agentic/widget events to the technical owner.
Avoid sending sensitive chat content to Slack.
Review recipients when team members leave.