How to Add Slack Notifications for Critical Alerts
Aideworks can post alerts directly to a Slack channel — so your team sees critical issues the moment they're detected, without waiting for an email to land in their inbox. This guide covers the full setup in under 10 minutes.
Before you start
- An Aideworks account with at least one domain being monitored.
- A Slack workspace where you have permission to add apps (or ask your Slack admin to approve).
- A Slack channel to receive alerts — this can be an existing channel or a dedicated one like
#infra-alerts.
Why use a dedicated Slack channel?
Routing monitoring alerts to a shared #general or #team channel creates noise. A dedicated #infra-alerts or #monitoring channel with the right people subscribed ensures alerts are seen immediately and don't get buried.
For MSP setups managing multiple clients, consider a channel per client workspace (e.g. #client-acmecorp-alerts) so client-specific incidents are isolated and easy to search.
Step 1 — Open Notifications settings
In Aideworks, navigate to Settings → Notifications. You'll see the three notification channels available on your plan: Email, Slack, and Webhook.
Under Slack, click Connect a Slack workspace.
Step 2 — Authorise Aideworks in Slack
You'll be redirected to Slack's OAuth authorisation screen. Review the permissions Aideworks requests:
- Send messages as Aideworks — posts alert messages to a channel you choose.
- Read your workspace name — used to display the connected workspace in your settings.
Aideworks does not request access to read existing messages or access to files or DMs. Click Allow to complete the authorisation.
Note: If your Slack workspace requires admin approval for new apps, you may see a request submitted to your admin instead of immediate access. Share the Aideworks app listing with your Slack admin to expedite approval.
Step 3 — Choose a channel
After authorization, you're returned to Aideworks. From the Slack channel dropdown, select the channel where alerts should be posted.
If you want alerts in a private channel, invite the Aideworks app to that channel first: open the channel in Slack, type /invite @Aideworks, and press Enter. The channel will then appear in the dropdown.
Step 4 — Configure which alerts trigger Slack
Not every alert needs to interrupt a Slack channel. Use the alert filter to control which severity levels and event types post to Slack:
| Alert type | Recommended Slack setting |
|---|---|
| SSL certificate expiry — Critical (≤14 days) | Send to Slack |
| SSL certificate expiry — Warning (≤30 days) | Email only |
| DNS record change — NS or MX | Send to Slack (Critical) |
| DNS record change — Other | Email only or Slack summary |
| Uptime — domain down | Send to Slack (Critical) |
| Uptime — domain restored | Send to Slack (resolved notification) |
| Email security — DMARC change | Send to Slack (High) |
Set these filters in Notifications → Slack → Alert filter. Toggle severity checkboxes per monitoring type to match your team's escalation workflow.
Step 5 — Test the integration
Click Send test alert in the Slack notification section. A test message is posted to your chosen channel immediately. Verify it arrives formatted correctly with:
- The alert type and severity badge
- The affected domain name
- A direct link to the domain detail page in Aideworks
- The timestamp of the alert
If the message doesn't arrive, check that the Aideworks app is a member of the channel (especially for private channels) and that the channel name in settings matches exactly.
Routing alerts to multiple channels
Aideworks supports connecting multiple Slack channels with different filters. For example:
- A
#monitoring-criticalchannel receives only Critical and High severity alerts (SSL expiry, NS changes, downtime). - A
#monitoring-logchannel receives all alerts as a full audit trail.
Add additional channels via Notifications → Slack → Add channel.