Webhook notifications
Optional, outbound keyword-match alerts to Discord, Telegram, or your own endpoint.
Webhook notifications are optional, outbound keyword-match alerts. Create named destinations on your account page, then pick one from the dropdown per schedule in Advanced options → Keyword monitoring. A schedule needs at least one keyword rule before it can use a webhook.
Supported destinations
- Discord: an HTTPS incoming webhook URL on
discord.com. - Telegram: a bot token and a chat ID or
@channelusername. - Generic: one user-selected HTTPS endpoint that accepts a JSON
POST.
Chrome requests access only to the selected destination origin when you save the schedule. Generic endpoints are HTTPS-only; redirects are refused. There are no custom headers, custom bodies, retries, or background polling. Delivery has a 10-second timeout and is limited to one attempt per minute per schedule to avoid flooding a destination.
Payload and privacy
By default, a webhook receives a title, the matching value, and the timestamp. The generic JSON body is:
{
"event": "keyword_match",
"occurredAt": "2026-07-26T12:00:00.000Z",
"schedule": { "id": "…", "title": "My schedule" },
"match": "available now"
}Include the target URL is off by default. When enabled, targetUrl is added after removing credentials and fragments and redacting
every query-string value. Page text is never sent. Discord delivery disables all
mentions; Telegram uses plain text with no parse mode.
Webhook URLs and Telegram bot tokens are saved to your account encrypted at rest so every linked device can offer the same named destinations; on devices they live only in local extension storage, and they are deliberately omitted from schedule exports. Treat them as credentials: do not share screenshots or storage dumps containing them, and rotate them in Discord or Telegram if exposed.
The wire formats follow Discord's Execute Webhook endpoint and Telegram's sendMessage API.