Notifications¶
Notifications tell you when a Monitor detects a change or fails to run. (Uptime has its own separate alert emails — see Uptime — not covered by anything here.) On a Business plan, you can also send these events to Slack or Microsoft Teams via a webhook — see API Access — independently of the email settings below. When the change is a new JS console error, the email and webhook message include the error text itself, not just a "something changed" flag.
Connect and route integrations¶
VisualRunner separates a shared workspace connection from a project's routing choices:
- Open Workspace settings → Connections to see services authorized for the workspace. Jira Cloud is connected once here and then reused by projects.
- Open a project and choose Integrations to map that project to Jira and configure its notification destinations.
- For Slack, Microsoft Teams, or generic JSON delivery, select the provider, paste its webhook URL, and choose one or more events: Visual change, Run failed, or Repeated failure.
- Select Add destination, then use Test before relying on it for a live monitor.
- Use Disable to pause delivery without deleting configuration, or Delete to remove the destination permanently.
Destinations created from a project's Integrations page receive events from that project only. Use different destinations when separate teams or channels own different projects. Webhooks and Jira/automation are Business-tier features; see Plans & Billing.
Treat webhook URLs as secrets: anyone holding one may be able to post into the destination. Do not paste them into screenshots, tickets, or public logs. Rotate a URL at the provider if it is exposed.
The notification bell¶
Click the bell icon in the dashboard header to see recent activity across every project you have access to — not just the one you're currently viewing. Unread items are highlighted; clicking one marks it read and takes you to the relevant comparison (or the monitor list, if it's a run-failure notification with no specific comparison to show).
Email notifications¶
Each monitor has its own notification preferences (see Monitors):
- Email on change — a detected visual/status/redirect change.
- Email on failure — the monitor couldn't complete a run.
-
Frequency — Immediate (one email per event), Daily digest, or Weekly digest (Sundays).
-
Recipients — All members assigned to the project (the default), or the monitor creator only.
Project-restricted members see bell notifications and receive project-member emails only for their assigned projects. Reading a notification affects only your own account, not anyone else's unread count.
Digests bundle up everything that happened in the period into one email instead of one per event — useful for a monitor that changes often and doesn't need instant attention.
Escalation¶
If a monitor fails three runs in a row, you get an extra "repeated failures" email on top of the normal failure notification — a signal that this isn't a one-off blip. Escalated-failure notifications are not cleared by "Mark all read" — you need to open and dismiss each one individually, so it doesn't quietly disappear in a bulk clear.