Send alerts to Slack

What you need first

Slack alerts are on the Business and Agency plans. You also need to be allowed to add apps to your Slack workspace. Some workspaces ask an admin to approve new apps first — if yours does, Slack sends them the request when you connect.

If your workspace doesn't allow apps at all, you can still paste a webhook URL instead — see “Use a webhook URL instead” below.

Step 1 — Open Alert settings

In Relvato, open the account menu at the top right and choose Alert settings. Slack has its own section there.

Step 2 — Click Add to Slack

Slack opens its own screen and asks which channel Relvato should post to. Pick one — a shared channel such as #site-alerts works well, so the whole team sees failures — and click Allow.

You land back in Alert settings with “Slack connected — alerts will post to #your-channel”. Each Relvato account posts to one channel; to switch, use Change channel and pick another.

Step 3 — Send a test

Click Send test to Slack. A message from Relvato should appear in the channel within a few seconds. If it doesn't, check you're looking at the channel you picked, then see “If Slack alerts stop” below.

Choose what reaches Slack

Slack follows the same “Alert me on” severity level as email. Set it to critical and a broken checkout gets through while a cosmetic warning doesn't.

Slack gets alerts as they happen, so keep “As it happens” ticked under How often. The daily and weekly digests are email only — if you untick “As it happens”, nothing is posted to Slack.

A check posts when it starts failing, not again on every re-run while it stays broken, so a channel isn't flooded by one outage. When you run a check yourself and it fails, that posts too. Tick “Tell me about every run” if you also want a note when checks pass.

Email and Slack have separate switches: untick Post alerts to Slack to pause Slack without touching email, or the other way round.

What a message contains

Each alert names the site and the check, the error it found, its severity, what triggered the run (for example a plugin update or a deploy), and a View run button that opens the run in Relvato with its screenshot.

A message that says a check couldn't run — for example “Cloudflare blocked Relvato” — is about access, not a broken page: the check never reached your site. The firewall allowlist guide fixes that.

Use a webhook URL instead

If you can't install apps in your workspace, create an Incoming Webhook in Slack (Apps → Incoming Webhooks → Add to Slack), choose a channel, and copy the URL it gives you. In Alert settings, open Or paste a webhook URL, paste it, and save.

Anyone with that URL can post to the channel, so Relvato stores it like a password and never shows it again.

If Slack alerts stop

If the Relvato app is removed from your workspace, the channel is archived, or a Slack admin blocks posting, Relvato notices, stops using the connection, and tells you: the notification bell shows “Slack alerts stopped” with the reason, and Alert settings shows the same. Click Reconnect Slack and pick a channel to start again.

Relvato only disconnects when Slack says the connection is gone for good. A Slack outage, a timeout or a rate limit never disconnects you — the next alert simply tries again.

Disconnect Slack

In Alert settings, tick Disconnect on save and click Save preferences. Relvato deletes the webhook and the channel and workspace details straight away — see the privacy policy for exactly what's kept and when.