Understand the delivery path
An alert needs an eligible state change and a matching route. Service-based routes also need working organization credentials. Configure this in Settings → Alerts for the selected organization.
The Consecutive failed checks before alerting setting controls how many failures are needed before an endpoint down notification becomes eligible. It applies across the organization. Increasing it reduces transient alerts but delays notification. Maintenance, pausing, muting, and delivery batching can also explain why a failed check does not immediately produce a message.
Connect a delivery service
An organization owner or admin can add delivery-service credentials. Supported options in the app include Slack, Discord, PagerDuty, Opsgenie, Twilio SMS, Pushbullet, ntfy, Gotify, and webhooks, alongside email routes. Use the provider-specific fields displayed in the form; available choices depend on your organization's configuration.
Save a named connection so routes can reuse it. Use a dedicated provider credential where possible, and avoid putting credentials in monitor names, incident updates, screenshots, or public descriptions.
Create a route
- Under Create an alert route, select the channel.
- Select the connected service when required, or enter the destination requested by the form.
- Choose what the route Covers and select the relevant group, endpoint, or Nexus Point where applicable.
- Save and review Active routes to confirm the destination and coverage.
Endpoint and group routes receive failed-check and recovery notices. Nexus routes receive aggregate state transitions. Pro supports teammates and per-user alerting; the controls you can edit also depend on your organization role.
Verify delivery
Use the test action on a connected service and confirm the message at the destination. A successful save only proves the configuration was accepted. Email and SMS require a real alert to verify receipt. Exercise failure and recovery with a temporary monitor you control and account for the configured failure threshold.
If receipt fails, verify both halves of the setup: the service credential and the active route. Check revoked provider tokens, channel permissions, destination spelling, endpoint coverage, and the monitor's alert eligibility. See troubleshooting.
Maintain routing
Review routes when teammates leave, a group changes purpose, or a provider credential rotates. Remove obsolete routes to prevent duplicate notices. For timed paging and acknowledgement, configure native on-call in a Pro organization.