Notifications and digest
Choose where Watari posts updates, configure the daily digest, and manage archived-channel rechecks.
Configure how and where Watari notifies you and your team when something noteworthy happens in the pipeline.
Notification preferences are per-user. Each teammate manages their own email and in-app toggles from Settings → Notifications. Workspace admins additionally control which Slack channels receive workspace-level routing.
Where Watari posts
Watari can notify you through three channels:
- Email: sent to your account email address. Each event type has its own toggle.
- In-app notifications: appear in your Inbox in the Watari dashboard. Some event types have the in-app notification locked on (critical bug alerts, usage warnings, billing actions), these can't be silenced because they require immediate attention.
- Slack: workspace-level routing to specific channels. Set by admins in Settings → Notifications → Channel routing. Requires a Slack integration (see Routing and notifications, Slack channel-invite step and OAuth setup).
Event types
| Event | In-app | Notes | |
|---|---|---|---|
| Bug created | Toggle | Toggle | Fires when a new bug is extracted from a ticket |
| Bug status changed | Toggle | Toggle | Fires when a bug moves through the pipeline |
| Draft PR ready | Not available | Toggle | A draft pull request was opened for a bug. In-app only |
| RCA ready | Not available | Toggle | A root cause analysis is ready for your review. In-app only |
| Critical bug alert | Toggle | Always on | Critical-severity bug detected |
| Daily digest | Toggle | Not available | Email-only; on by default |
| Pipeline failed | Toggle | Toggle | Admin-only; ticket processing error |
| Usage warning | Toggle | Always on | Admin-only; 80% or 100% of Mapped Issue allowance |
| Integration disconnected | Toggle | Toggle | Admin-only; OAuth token expired or revoked |
| Billing action needed | Toggle | Always on | Admin-only; payment failed or trial ending |
Admin-only events are shown only to workspace owners and admins. Members do not see or configure them.
Daily digest
The daily digest is a per-user email summarizing the previous 24 hours of activity in your workspace. It is on by default for every teammate:
- New bugs extracted (count by severity)
- New Mapped Issues (top 5, sorted critical-first)
- Tickets processed count
The digest runs at 8:00 AM UTC every day and is sent to every teammate who has not turned off the Daily Digest email toggle. Orgs with no activity in the previous 24 hours don't receive a digest that day.
To stop receiving it, go to Settings → Notifications and turn off the Daily Digest email toggle, or use the unsubscribe link in any digest email.
Channel routing
Workspace admins can configure which Slack channels receive which event types from Settings → Notifications → Channel routing. For example:
- Critical-severity bugs →
#incidents - All other Mapped Issues →
#bugs - RCA published →
#product-updates
Routing is configured per-event-type per-channel. Events that don't have a configured routing destination still appear in the default Slack channel chosen during the Slack OAuth connection.
Archived-channel recheck
If a Slack channel gets archived after Watari is configured to post there, Watari detects the error and pauses posting to that channel. It doesn't retry indefinitely, instead, it marks the channel routing as errored and runs a monthly background recheck.
When the background recheck runs and finds the channel is available again (unarchived, or the bot was re-invited), posting resumes automatically. You don't need to manually reconnect or reconfigure the channel routing.
If you want to trigger a recheck manually rather than waiting for the next scheduled pass, visit Settings → Integrations, find the Slack integration, and click Recheck.
Next: Invoices, credits, and caps: mismapped credit window and overage cap configuration: download invoices, understand the mismapped credit window, and configure overage behavior.