Choose where scheduled tasks and page monitors send alerts. Set up channels in Settings → Notifications, then pick the channels for each task.

These settings apply to scheduled tasks and page monitors. They do not add alerts to regular chats. Reports started with /research have their own browser notification when ready.

Choose a channel

Channel	Setup
Browser notification	Allow Chrome notifications in your browser and operating system.
Email	Sign in to Starizon. Alerts go to the account email shown in Settings.
Webhook	Enter a receiving URL, with the method and headers that service requires.
Push (ntfy)	Set up a server and topic, then subscribe to that topic in the ntfy app.

Use Send test notification for each channel you plan to use. Then open the scheduled task or monitor and pick the channel under Notify via. A task created through /schedule or /monitor starts with browser delivery; configuring email or push in Settings alone does not select it for that task.

Browser and email alerts

If the browser test passes but no alert appears, check your operating system’s notification permissions and focus settings. For email, confirm the account address shown and check spam or filtering rules.

Starizon email alerts use credits. The page check still runs in your browser when you choose email.

Webhooks

The default webhook sends a POST request with the notification’s title, message and URL. Use a receiver that accepts that format, or set up a relay for the service you want to notify.

Some services expect a different payload from a generic webhook. Reaching the URL does not prove the receiving app showed the message, so check the receiver after you send a test.

Put credentials and custom headers in the channel settings. Keep them out of task prompts and shared screenshots.

Push with ntfy

Generate a random topic in Settings and subscribe to the topic URL it shows in the ntfy app. Add an access token when the server or the selected forwarding option requires one.

Treat the topic name like a password: anyone who knows a public topic may be able to subscribe. If you turn on screenshot attachments, the push service receives the page capture along with the notification.

Check delivery separately from the task

A task can finish while its notification fails. Monitor history shows whether the condition matched and whether the alert was sent. If an alert is waiting, failed or was skipped, read the reason there. For a delivery problem, fix the channel and send a test before changing the monitor’s condition.

Page monitors covers repeated-alert settings, and Data and privacy covers what leaves the browser.