Connecting alert channels
In Integrations and API, choose a service, enter the details, and save the alert contact. The Test button sends a real test message. Then assign the alert contact in the monitor settings. A monitor with no assigned alert contacts uses all active alert contacts in the account; if it has only disabled alert contacts assigned, it doesn’t send alerts anywhere.
Microsoft Teams
In the target channel, open Workflows and the template for receiving a webhook and posting a message to the channel. For authentication of the incoming request, choose Anyone and copy the generated HTTPS URL. It’s a secret: anyone who knows the address can post messages to the flow. digiWatcher sends an Adaptive Card version 1.2.
The flow needs an active owner and a working connection to Teams. Add a co-owner so that one person leaving doesn’t stop delivery. A confirmed webhook receipt doesn’t yet mean the message appeared in the channel—check the first Test there.
Microsoft’s guide to webhooks and WorkflowsGoogle Chat
In the space, open Apps & integrations → Add webhook. Copy the whole address, including the key and token parameters. You need Google Workspace with incoming webhooks allowed; if the option is missing, your organization’s administrator has to allow it.
Google’s guide to creating a webhookOther channels
- Email: just the recipient’s name and address.
- Telegram: create a bot with @BotFather, then enter the token and chat ID. Message the bot first.
- Slack: enter the Incoming Webhook URL from your Slack app’s settings.
- Discord: Channel settings → Integrations → Webhooks.
- ntfy: enter the URL of a hard-to-guess topic and subscribe to it in the mobile app.
- Pushover: you need the application’s API token and your User Key.
- Webhook: enter the URL of your n8n workflow or another JSON receiver. We send event, monitor_id, monitor, url, cause, downtime_ms, at, and text. The receiver therefore has to be trusted.
Delivery and errors
Operational alerts go through a persistent queue. If delivery fails, it’s retried, up to six attempts. The test button makes one immediate attempt. You can see the results with your alert contacts under recently sent alerts; an HTTP error means the receiving service rejected the message. Check that the webhook is valid and that its owner has the required permissions.
Webhooks have a timeout and protection against access to internal networks. A successful HTTP response confirms that the service received the message, not that a person read it. For an outage of the whole app, there’s separate external monitoring.