Notifications
Route competitor alerts to where your team already works: email, Slack, or a custom webhook.
Configure delivery in the app under Workspace settings → Notifications. Rules control which monitors fire, minimum severity, and whether delivery is realtime or batched into a digest.
Channels
| Channel | Best for | Setup |
|---|---|---|
| Daily/weekly rollups, inbox triage | Enabled by default on your account email | |
| Slack | Team channels, quick awareness | Paste a Slack incoming webhook URL |
| Webhook | CRM, internal tools, automation | Paste an HTTPS endpoint URL; optional signing secret |
Delivery modes
| Mode | Behavior |
|---|---|
| Realtime | Sends as soon as a change passes your severity rule |
| Digest | Batches changes into a window (1d, 7d, etc.) and sends one summary |
Email digests roll up across workspaces on your account. Slack and webhook digests are sent per workspace integration.
Digest scope: Notification digests (digest.ready webhooks and email batches) include only changes buffered in the flush window for that integration. The API digest covers the full workspace period with synthesized bullets and live coverage stats. Both use the same needs_review.items[] field shape — see Webhooks.
Notification rules
Rules are evaluated in priority order:
- Monitor-specific rule
- Monitor-type rule (e.g. all pricing monitors)
- Workspace default
Each rule sets allowed channels, minimum severity, and delivery mode.
Test your integration
Use Test next to Slack or Webhook in settings. Slack receives a short message; webhooks receive a test.ping event.
Webhook payload reference
For envelope fields, signing, dedupe, and JSON examples, see Webhooks.
API and agents
The same interpreted changes are available over the REST API and MCP server. Webhooks push to you; the API and MCP pull on demand.