Notifications
Send real-time alerts to your team when a new error is captured or a new lead is submitted.
Supported Channels
| Channel | Trigger |
|---|---|
| Slack | New error (first occurrence or re-open), new lead |
| Telegram | New error, new lead |
| New error, new lead | |
| Webhook (n8n) | New error, new lead |
| In-app (WebSocket) | New error, new lead |
Configuration
All notification settings are per-site, configured in Dashboard → Sites → [Site] → Settings.
Slack
Slack Webhook URL: https://hooks.slack.com/services/T.../B.../...
Create the webhook in your Slack workspace: App Directory → Incoming Webhooks → Add to Slack.
Telegram
Telegram Bot Token: 123456789:ABCDEF...
Telegram Chat ID: -1001234567890
- Create a bot via @BotFather — save the token
- Add the bot to your group/channel
- Get the chat ID from
https://api.telegram.org/bot<token>/getUpdates
Email
Email Notify: enabled
Notification Email: team@yourdomain.com
Requires SMTP_* environment variables to be set on the Platform server — see Configuration.
Webhook (n8n)
n8n Error Webhook URL: https://n8n.yourdomain.com/webhook/...
n8n Leads Webhook URL: https://n8n.yourdomain.com/webhook/...
The Platform sends a POST request with a JSON payload. You can use n8n to route notifications to any other system (PagerDuty, Jira, WhatsApp, etc.).
Notification Logic
- New error: fires when an error is created for the first time (first occurrence)
- Re-opened error: fires when an error previously marked
resolvedorignoredis received again - Errors marked
muted: never trigger notifications, even on re-open - Errors marked
ignored: do not trigger notifications after the initial one - New lead: fires when the lead is captured
- New chat: fires when a visitor starts a new conversation — email, Slack and Telegram only, never the webhook, because a chat transcript is held for you to read in the dashboard
- Abandoned checkout: fires after the delay set below, if the shopper still has not paid
Abandoned checkout alerts
A checkout lead is captured the moment a shopper fills in the first field — which is usually a few minutes before the payment goes through. Two settings under Settings → Notifications decide when, and whether, you hear about it.
Wait before alerting is how long we hold the alert. Set it to 15 or 30 minutes and you stop telephoning people who are still on the payment page. If the shopper completes the purchase while we wait, the abandoned-cart alert is dropped and you are told about the order instead — you never lose the news, only the wrong version of it. The alert also goes if they close the tab; the delay costs you nothing except the wait.
Minimum cart value is a floor in your shop's own currency. Below it, nothing is sent to Slack, Telegram or email. The lead is still captured, still in the dashboard and still in your notification bell — the floor only stops the interruption.
Two things worth knowing:
- The basket is measured when the alert is due, not when it was captured. A shopper who keeps adding items and crosses your floor while you wait still reaches you.
- Setting a floor adds up to five minutes of waiting even with the delay at 0, because the basket has to be re-read before it can be compared. Alerts go out on a five-minute cycle, so any delay you set is a minimum rather than an exact time.
An alert is also dropped if somebody on your team has already reached out to that lead, or muted recovery for it, or if the lead was deleted — and if the platform was down for a day, an alert more than 24 hours late is dropped rather than arriving as stale news.
Webhook Payload Format
Error notification
{
"event": "new_error",
"siteId": 1,
"error": {
"id": 42,
"message": "Cannot read property 'x' of undefined",
"source": "https://mysite.com/app.js",
"status": "new",
"occurrenceCount": 1,
"firstSeenAt": "2024-01-15T10:00:00Z"
}
}
Lead notification
{
"event": "new_lead",
"siteId": 1,
"lead": {
"id": 17,
"email": "customer@example.com",
"firstName": "Jane",
"cartTotal": "89.99",
"capturedAt": "2024-01-15T10:05:00Z"
}
}
In-App Real-Time Alerts
The dashboard uses a WebSocket connection (Socket.IO) to push notifications in real time to any browser that has the dashboard open. Alerts appear as a toast notification in the top-right corner without requiring a page refresh.