What this guide covers
A notification action is an output of a task rule, not a remote monitor. Watch must still capture and recognize the shared source. You can choose several channels independently for a task: an in-page notice, a system browser notification, a Webhook, Telegram or email through a configured interface. A channel being selected does not prove it is configured or reachable.
Set it up
Begin with an in-page notification and a known matching condition. Next, authorize system notifications from the browser controls if needed, and check operating-system notification settings. For remote delivery, configure the chosen service in settings, use its test control and then trigger a real task once. Review the resulting delivery status instead of only checking whether the rule matched.
Check the result
Webhook configuration can target supported Slack or Discord-style endpoints. Telegram requires your Bot Token and Chat ID. Email requires an endpoint that you provide; entering a recipient is not a built-in hosted mail service. Keep service credentials private, use test content first and remove or rotate a token if it has been exposed in a screenshot or shared browser profile.
Before you rely on it
Browser requests are subject to endpoint availability and cross-origin permissions. A URL that works from a server or command-line tool may not accept the same browser request. Inspect a failed action’s status and the destination’s documented request contract. Do not disable browser security controls or paste secrets into public support threads to make a test succeed.
Troubleshooting
System notifications can be suppressed by browser permissions, operating-system focus modes or notification settings. Sound also depends on browser audio policies and may need a user interaction to unlock it. Use the built-in sound preview, then test the actual event. Neither a silent notification nor an in-page success proves that a remote service delivered a message to a person.
Product reference
External channels can transmit recognized text and task context to the service you configured. Reduce the region and message sensitivity before enabling them on a work or private screen. Local OCR is compatible with intentional remote notifications, but the two stages have different data boundaries. Disable unused channels and confirm recipients before leaving a test configuration in place.
Yes. Select in-page, system, Webhook, Telegram and email notifications independently for each task. Webhooks support Slack and Discord. Telegram needs a Bot Token and Chat ID; email needs your own notification endpoint.
Further reading
- Privacy boundaries and local versus cloud translation
- Screen sharing and browser permissions
- Color changes and reference-image matching