Solution

Slack and webhook alerts for website changes

Route every detected change to the channel your team already lives in. One field on the monitor, a formatted Slack message or a JSON webhook, no extra setup.

Start free trial How it works

Most teams find out about a website change hours after it happens, because the alert sits unread in an inbox. WebMonitor.fyi can post that alert into Slack instead, in the channel people already watch all day. Each monitor takes an optional Slack webhook URL or a generic webhook URL. When a check trips your criteria, the alert goes to email and to those destinations at the same time. The Slack message arrives formatted, with the site, what changed, and a link back to the dashboard. The generic webhook sends clean JSON, so you can pipe alerts into a ticketing system, a Zapier or Make automation, or any script you run yourself. From there you can pass them on to Discord, Microsoft Teams, or anywhere else.

What it does

Formatted Slack messages

Alerts post as a Slack Block Kit message, not a wall of raw text. You get a header, the monitored site, your criteria, a plain-English summary of the change, and a button that opens the monitor.

Generic JSON webhooks

Point a monitor at any https endpoint and WebMonitor POSTs a small JSON payload on each alert. Send it straight to a Zapier or Make hook, a ticketing queue, or a script you wrote. Tools like Discord and Teams want their own format, so route those through a relay.

Per-monitor routing

Each monitor carries its own Slack and webhook fields. Send price drops to a deals channel and competitor changes to a strategy channel, without mixing the two.

Email still runs

Turning on Slack or a webhook does not switch email off. The email alert sends first, every time. The other channels fire alongside it, so a webhook outage never costs you the notification.

Safe by default

Destination URLs must use https and resolve to a public host. WebMonitor blocks private and internal addresses, and never follows a redirect, so a webhook cannot be pointed back at your own network.

How to set it up

Create a Slack incoming webhook

In Slack, add the Incoming Webhooks app, pick the channel you want, and copy the webhook URL Slack gives you. This is the only setup that happens outside WebMonitor.

Open the monitor notification settings

Add a new monitor or edit an existing one. Under Notifications you will see optional fields for a Slack webhook URL and a generic webhook URL.

Paste the URL and save

Drop the Slack URL into the Slack field, or any other https endpoint into the webhook field. Leave a field blank to skip that channel, then save the monitor.

Get alerts where you work

The next time the monitor trips, the alert lands in Slack and on your webhook within the same run as the email. Clear a field later to turn a channel back off.

Common use cases

Engineering teams piping deploy-page and status changes into an on-call channel
Sales and strategy teams watching competitor pricing changes in a shared Slack room
Customer-success teams routing new negative reviews to a triage channel
Ops teams forwarding alerts into a Zapier or Make automation that fans out to Teams or Discord
Developers wiring change alerts into Zapier, a ticketing queue, or a custom script
Compliance teams sending regulatory page changes into a docketing workflow

Honest limits

WebMonitor sends one message per alert; it does not host a two-way Slack bot, so you cannot reply to an alert and have the monitor act on it. Slack and webhook delivery is best-effort: if the destination is down or slow, that single message can be missed, though your email alert and the dashboard history still hold the record. Destination URLs have to be public https endpoints, so an internal-only webhook behind a VPN will not work without exposing it first.

Frequently asked questions

How do I send website change alerts to Slack?

Create an incoming webhook in Slack for the channel you want, copy the URL, then paste it into the Slack field on any WebMonitor monitor. The next time that monitor detects a change matching your criteria, WebMonitor posts a formatted message to the channel automatically.

Do Slack alerts replace email alerts?

No. Email always sends first on every alert. Slack and webhook messages fire alongside it in the same run, so adding a channel never turns email off. If a webhook fails or times out, your email alert and the dashboard history are unaffected.

Can I send alerts to Discord or Microsoft Teams?

Yes, with one extra hop. WebMonitor posts its own JSON shape, and Discord and Teams each expect a specific payload format, so you route the webhook through Zapier, Make, or a small relay that reshapes it. Slack is the exception: the Slack field is formatted for Slack, so it posts to a Slack incoming webhook directly.

What does the webhook payload contain?

A small JSON object with the event name, the monitor ID, the site hostname, the full URL, your criteria, a plain-English summary of the change, the time it was detected, and a link to the dashboard. It is stable and easy to parse in any language or automation tool.

Is it safe to send alerts to a webhook?

WebMonitor only accepts public https URLs and checks the destination on every send, blocking private and internal addresses and refusing to follow redirects. That stops a webhook from being aimed back at an internal network. Treat the URL itself as a secret, since anyone holding it can post to your channel.

Does this cost extra?

Slack and webhook alerts are part of your plan, with no separate add-on fee. Check the pricing page for what each plan includes. Delivery rides on the same checks you already run, so turning on a channel does not change your monitoring frequency or job count.