Direct setup
Send alert and recovery messages to an email recipient.
Workspace email delivery with provider diagnostics.
14 current integrations · 4 categories
Send every signal where work already happens.
Connect Monitoring.app to chat, on-call, automation, and PSA tools. Route failures and recoveries with enough context to act—without copying alerts between systems.
Integration catalog
One signal. Many destinations.
3
Routing lanes
1→1
Episode links
Test
Before routing
Current capabilities
Built for the full path from detection to follow-up
Each category has its own job. Notifications reach people, incident response manages urgency, automation carries structured events, and PSA integrations maintain the ticket lifecycle.
Notifications
Put the signal in front of the right person
Deliver failure and recovery context to the channels your operators already watch.
Direct setup
SMS
Send concise, urgent alerts to an E.164 phone number.
Plan-aware monthly usage and idempotent delivery.
OAuth
Slack
Post one-way alerts to a selected Slack channel.
Failure and recovery messages with monitor context.
OAuth
Microsoft Teams
Post one-way alerts through the Monitoring.app Teams bot.
Route monitoring events to a team or channel conversation.
OAuth
Discord
Post one-way alerts to a selected Discord channel.
Channel messages for failure and recovery events.
Direct setup
Webhook
Send a versioned JSON event envelope to your HTTPS endpoint.
HMAC-SHA256 signatures and stable delivery identifiers.
Incident response
Open the incident. Resolve it on recovery.
Turn a monitoring episode into an incident lifecycle without asking operators to copy details by hand.
Direct setup
PagerDuty
Trigger and resolve PagerDuty incidents through Events API v2.
Stable deduplication keeps failure and recovery on one incident.
Automation
Turn monitoring events into your own workflow
Pass structured signal into no-code automation tools for the actions that are specific to your business.
Direct setup
Zapier
Send monitoring events to a Zapier Catch Hook.
Structured source, state, message, and episode context.
Direct setup
IFTTT
Trigger an IFTTT Maker Webhooks event.
Source name, current state, and alert message values.
MSP ticketing
Keep alert episodes and service tickets together
Create a ticket on failure, update the same provider record, and close or complete it when service recovers.
Direct setup
ConnectWise PSA
Create, update, and close ConnectWise service tickets.
Map events to a service board and closed status.
Direct setup
NinjaOne
Create and maintain NinjaOne tickets from alert episodes.
Reuse the linked ticket through failure and recovery.
OAuth
Jira Service Management
Create and resolve Jira Service Management requests.
Map cloud, service desk, request type, and resolve transition.
Direct setup
HaloPSA
Create, update, and close HaloPSA tickets.
Map alert episodes to ticket type and closed status.
Direct setup
Autotask PSA
Create, update, and complete Autotask tickets.
Map events to a company, queue, and completion status.
One connected workflow
From “down” to done.
Monitoring.app keeps the source event and external action connected, so a recovery can follow the same route and close the loop.
01
Detect
A monitor or backup source changes state.
02
Route
Rules choose the target, trigger, cooldown, and order.
03
Follow through
Send, trigger, automate, or update the linked ticket.
Built-in controls
Connect confidently
1
Route with intent
Send every source or only selected monitors and backup sources. Trigger on failure, recovery, or both.
2
Control the handoff
Set cooldowns and escalation order while notification, incident, and automation lanes stay independent.
3
Test before relying on it
Validate connections, send test events, and review recent provider responses without exposing credentials.
4
Protect every connection
Credentials are encrypted at rest, destinations are masked in the portal, and outbound URLs are safety checked.
Provider availability depends on deployment registration and the provider account or credentials you connect. Plan limits apply to alert channels and SMS usage.
Ready to close the gap after detection?
Start with the destination your team already watches, then add incident, automation, and ticketing routes as your workflow grows.