Deploy Hooks
Deploy Hooks — Catch Breakage the Moment You Ship
Every deploy is a risk. Broken bundles, missing assets, and misconfigured redirects slip through CI and reach production. Deploy hooks trigger an immediate Sitewatch website check the moment your deploy completes — so you catch breakage in seconds, not hours.
- Instant website checks triggered by your CI/CD pipeline
- Configurable CDN propagation delay — check after caches clear
- Root cause playbooks delivered with every post-deploy incident
Deploy completed
2:14 PM
Webhook received
POST /hooks/deploy
Website check triggered
12s after deploy
Asset validation
main.b7e3a.js — 404
Alert dispatched
6 alert channels
Why deploy hooks
Stop waiting for users to report post-deploy breakage
Vercel integration
Add a webhook URL to your Vercel project settings. Every deploy triggers an instant website check — no code changes needed.
Netlify integration
Configure a deploy notification webhook in Netlify. Sitewatch checks your site the moment the deploy finishes.
GitHub Actions
Add a single curl step to your workflow. Works with any GitHub Actions deployment pipeline.
Any CI/CD platform
Generic webhook endpoint works with Bitbucket Pipelines, GitLab CI, CircleCI, or any tool that can fire a POST request.
CDN propagation delay
Configure a delay between deploy and check to let CDN caches propagate. Avoids false positives from stale edge nodes.
Sub-60-second detection
From deploy completion to incident alert in under 60 seconds. Catch breakage before the first user hits your site.
Signed webhook verification
Each deploy hook includes a signing secret. Sitewatch verifies the HMAC signature on every request to ensure only your CI/CD pipeline can trigger checks.
4
CI/CD platforms supported
<60s
Deploy-to-detection time
200/day
Triggers on Pro plan
How it works
From deploy to diagnosis in four steps
Add webhook URL
Copy your deploy hook URL from Sitewatch and paste it into your CI/CD platform's webhook settings.
Deploy your code
Push to production as usual. When the deploy completes, your CI/CD platform fires the webhook automatically.
Website check runs
Sitewatch waits for the configured propagation delay, then runs a full website check on every monitored page.
Root cause delivered
If something broke, you get root cause classification, confidence scoring, and stack-aware fix steps — across any of your configured alert channels.
The difference
Deploying without hooks vs. with deploy hooks
| Feature | Without deploy hooks | With Sitewatch deploy hooks |
|---|---|---|
| Detection speed | Hours — next scheduled check | Seconds — triggered by deploy |
| CDN propagation | Not accounted for | Configurable delay before check |
| Root cause | Manual investigation | Automatic classification + fix steps |
| Coverage | Depends on check schedule | Every deploy, every time |
| Setup effort | N/A | Paste one webhook URL |
Detection speed
CDN propagation
Root cause
Coverage
Setup effort
FAQ
Frequently asked questions
Deploy hooks work with Vercel, Netlify, GitHub Actions, and any platform that can send a POST request to a webhook URL — including Bitbucket Pipelines, GitLab CI, CircleCI, and custom scripts.
Copy the webhook URL from your Sitewatch site settings and paste it into your CI/CD platform's webhook or notification settings. No code changes or SDK integration required.
You can configure a propagation delay (e.g., 30 seconds or 2 minutes) per deploy hook. Sitewatch waits for the delay to pass before running the check, so you don't get false positives from stale edge caches.
The Starter plan includes 3 deploy hooks with 50 triggers per day. The Pro plan includes 10 deploy hooks with 200 triggers per day. Each hook can be configured for a different site or environment.
Yes. Enable maintenance mode on any site to suppress alerts while you deploy or perform maintenance. Monitoring continues in the background so you have data, but no alerts fire until you turn maintenance mode off.
No. Deploy hooks are additive — they run an extra check immediately after deploys. Your regular scheduled website checks continue to run on their normal cadence.
Explore more