Get colour-coded Slack messages the moment a monitor changes state. Red for down, green for recovery, amber for warnings like expiring SSL certificates.
What the alerts look like#
Every alert arrives as a colour-coded attachment in the channel. Red for down or failed. Green for recovery. Amber for warnings like an expiring SSL certificate or a cron job running longer than expected.
You get the monitor name, what happened (DOWN, RECOVERED, SLOW), which project the monitor belongs to, and a last-ping timestamp. No HTML that Slack's preview mangles. Just a clean sidebar stripe and the fields you actually care about.
Before you start#
You need:
- A Slack workspace where you can create apps or incoming webhooks.
- A WatchCron account on any plan. Slack alerts work on Free, Starter, Pro and Business.
First time takes about two minutes. I timed myself on a client project last month: 38 seconds from clicking "Create App" to getting the test message. Most of the time goes to remembering the Slack workspace password.
Step 1 — Create a Slack app and webhook#
Go to api.slack.com/apps and create a new app (or pick an existing one). Turn on Incoming Webhooks under Features.
Click Add New Webhook to Workspace and pick the channel where alerts should land: #ops-alerts, #monitoring, whatever fits your team. Slack generates a URL that starts with https://hooks.slack.com/services/. Copy it.
| Where | What to do |
|---|---|
| api.slack.com/apps | Create app → Incoming Webhooks → turn on |
| Webhook page | Add New Webhook to Workspace → pick a channel |
| After authorising | Copy the https://hooks.slack.com/services/… URL |
Step 2 — Add the channel in WatchCron#
Go to Alerts → Channels → Add channel and choose Slack.
| Field | What to enter |
|---|---|
| Label | A name you'll recognise, e.g. "#ops-alerts" |
| Webhook URL | The URL you copied from Slack |
Click Save.
Step 3 — Test and assign monitors#
Hit Send test. A sample alert should appear in the Slack channel within seconds. If it doesn't show up, check that the bot is actually in the channel. Slack's API silently drops messages to channels where the app isn't a member.
Open any monitor and tick the Slack channel under Alert channels. One webhook handles every monitor you assign to it.
What to paste where#
| WatchCron field | Value | Where you find it |
|---|---|---|
| Webhook URL | https://hooks.slack.com/services/T00…/B00…/xxxx | Slack app → Incoming Webhooks |
Routing alerts to different channels#
Need separate channels for separate projects? Create multiple Slack channels in WatchCron, each pointing to its own webhook URL. A client project's cron failures land in #client-monitoring, your own infrastructure goes to #internal-ops.
I'd keep it to two channels max per project, though. More than that and the signal-to-noise ratio drops fast.
When Slack alone isn't enough#
Slack works great during office hours. At 3 a.m., not so much.
You can't acknowledge an incident from a Slack message directly: you need to click through to the WatchCron dashboard. If your on-call rotation needs phone escalation, pair Slack with PagerDuty or Opsgenie (both available on any plan), or add SMS alerts (Pro) or voice calls (Business).
Slack covers all seven monitor types: cron jobs, uptime, SSL, domain expiry, ports, blocklist, and Cloud Cron. The format is identical across all of them.