The right update.
On your terms.
Your monitor decides what matters. Notification settings decide how and when you hear about it. Email and webhooks are independent delivery methods.
Start with your account email schedule
In Notifications, enable change-notification emails and choose immediate, hourly, or daily delivery. Check the displayed timezone before setting a daily schedule or quiet hours.
Monitors using the account default share that schedule. Starter and Pro also include quiet hours, minimum email intervals, and per-monitor schedule overrides. These settings affect change notifications, not sign-in or essential account emails.
Digests group matching changes. No matching changes means no digest. Delivery can be delayed by the notification worker schedule or retries, so “immediate” does not mean a guaranteed instant arrival.
Choose delivery methods for each monitor
Open a monitor’s details and find Notifications for this monitor. Enable email, webhook delivery, or both. Turning off emails does not turn off webhook delivery or stop the monitor’s checks.
Keep the account email schedule for consistent behavior across your monitors. On Starter and Pro, choose a custom schedule for a monitor that deserves different timing. A monitor with its own schedule gets its own digest rather than joining the account-default digest.
The monitor’s checking frequency and its email schedule are separate. An hourly email digest does not make a monitor check hourly. Review Plans, checks & history for check allowances and retained changes.
Send changes to another tool with Pro webhooks
Set up your account’s HTTPS endpoint in Notifications, then enable webhook delivery on each monitor you want to connect. Each matching change can be delivered independently of email batching and quiet hours. You can use webhooks with email switched off.
The webhook reference covers payloads, signature verification, delivery history, and retries. You do not need the API to receive webhooks.
Expected an alert? Check these first.
- Was this the starting baseline? Creating a monitor does not send a change alert for content already present.
- Did the rule match? A recorded text change is not necessarily a matching alert. A threshold or phrase rule fires when its condition becomes true.
- Did the check succeed? Missing content, a blocked page, or a paused monitor can prevent a new comparison. Review the monitor’s latest status.
- Is delivery enabled in both places? Check your account settings and this monitor’s email or webhook setting.
- Is the email waiting? Review the effective schedule, timezone, quiet hours, and minimum interval. Check spam or other inbox tabs, too.
- Have you reached an allowance? After the plan’s alert-email allowance, email changes move to a daily account digest. Check and webhook allowances have their own limits; inspect Usage & plan.
Review delivery history in Notifications when available. If you contact support, include the monitor name, approximate time, and any visible error. Never include API tokens or webhook signing secrets.