Send visual regression alerts to thousands of Zapier apps.
Connect WebChange Detector to Zapier and send every new change into the tools your team already uses. Post to Slack, open Asana or ClickUp tasks, log changes in Google Sheets, or ping the on-call developer via Telegram when a checkout breaks. No custom code required.
Your alerts, your tools.
New-change trigger
Start a Zap as soon as a check run finds new changes. Each change comes with the page, device, change percentage, AI summary and a link to the before and after view.
Any app, any action
Pick the app and the action in the Zapier builder: a Slack message, a ClickUp or Asana task, a row in Google Sheets, an email or a text message.
Filters and paths
Filter on the website, the page or the change percentage, so only the changes that matter reach your developers.
Embedded builder
Configure and test your Zap directly inside your WebChange Detector agency dashboard with the embedded Zapier interface.
Team visibility
Route alerts to client-specific Slack channels or dedicated maintenance teams so regressions are triaged where work already happens.
Works with webhooks
Run Zapier alongside signed webhooks and the REST API. Use Zapier for team messages, and webhooks or the API for your deploy checks.
Your first Zap in six steps.
The Zapier editor is embedded in the dashboard, so you never leave WebChange Detector to build the flow.
Open the Zapier integration
In your dashboard, open Automations. The Zapier builder is right there, already filled in with your email address.
Sign in to Zapier
Sign in with your Zapier account, or create one, right from the dashboard.
Pick the app and action
Choose where changes should go: a Slack channel, a ClickUp or Asana task, a Google Sheets row, or a multi-step Zap of your own.
Connect your account
Connect with your WebChange Detector API token. Use a subaccount’s token to receive only that client’s changes.
Map the fields
Map the fields you need: website, page URL, page title, device, change percentage, AI summary and the link to the before and after view.
Test and turn on
Test the Zap with a sample change to check your Slack formatting or task fields, then turn it on. From then on your alerts run on their own.
Five Zaps worth stealing.
Each of these is one trigger and one action.
Slack alert
Post every new change into #maintenance-alerts with the AI summary and a link to the before and after view, so your team can review it in one click.
Trello card
Create a review card on your maintenance board for every new change, with the comparison link attached.
Google Sheets log
Add every change as a row with website, page, date, change percentage and comparison link. A running record of what changed and when, on every client site.
Asana task
Open an urgent task for the lead developer when a key page breaks or goes blank, with the AI summary already in the description.
Telegram for the money pages
Send changes on checkout, cart or lead form pages straight to the on-call phone via Telegram or SMS, so someone looks before clients notice.
Build your own
Combine the new-change trigger with Zapier paths and filters: changes on your biggest clients go to their account manager, everything else is logged quietly.
Route by website, page or size of change.
Zapier’s filters and paths let one account handle hundreds of client sites: send changes on key pages to an urgent Slack channel, log everything in Google Sheets, and route checkout changes to Telegram. One Zap can cover your whole client list without managing individual webhooks.
If you outgrow the no-code layer, the same events are available raw: webhooks deliver the full data to your own endpoint, and the REST API covers everything else. All three run side by side.
Frequently asked questions
How does WebChange Detector integrate with Zapier?
Through the WebChange Detector app on Zapier and its new-change trigger. When a check run finds new changes, from Monitoring, an On-Demand Check or an Auto Update Check, the trigger fires with each change: page, device, change percentage, AI summary and the link to the before and after view.
What payload fields are available in the Zapier trigger?
Among others: url, html_title, device (desktop or mobile), group_name, difference_percent, status, ai_summary (a short plain-language description of what changed), public_link (the before and after view, no login needed) and created_at.
Can I filter Zaps so our maintenance team only receives real alerts?
Yes. Add a Filter by Zapier step, for example on the page URL or the website name, so only changes on key pages reach the team. AI verification already keeps much of the usual noise out.
Can I route alerts to different Slack channels based on the client site?
Yes. Use Zapier Paths on the group_name or url field to send client A to #client-a-alerts and client B to #client-b-alerts, or send your biggest online shops to an on-call channel.
Do I need a paid Zapier plan to use this integration?
That depends on your Zapier plan, not on WebChange Detector. Simple two-step Zaps, like the trigger plus a Slack message, run on Zapier’s free plan. Filters, paths and longer Zaps need a paid Zapier plan. Check Zapier’s pricing for the current limits.
How does Zapier compare to native Webhooks?
Zapier is the fast, no-code way into team tools like Slack, ClickUp, Asana and Google Sheets. Webhooks fit your own backend systems and deploy checks, where you want the raw JSON and verify each delivery yourself.
What happens if a website experiences a White Screen of Death (WSOD)?
A page that turns blank always triggers an alert. The change reaches your Zapier trigger like any other, with the AI summary and the before and after link, as soon as the check run is done.
Related pages.
Catch the next visual bug before anyone else.
Start with a free trial, connect a site, and see your first before and after comparison today.