Frontend deploys
Rewarm marketing and app shells on Vercel/Netlify.
← Back to features
Feature
Deploy & CI Triggers
Rewarm automatically when you ship—Vercel, Netlify, Shopify, and more.
Deploys are a common cause of cold caches. Deploy triggers let Vercel, Netlify, Shopify, or custom CI call Cache Rocket with your API keys to start matching warmers or priority-warm specific URLs right after ship.
Highlights
- Webhook endpoints for major platforms
- Authenticate with public and secret API keys
- Optional crawler ID and URL lists in the body
- Shrink the cold window after every release
Warm as part of go-live
Treat cache warming like a release checklist item—automated. When the deploy succeeds, warming starts without a human opening the dashboard.
Flexible payloads
Send a hostname to match warmers, pin a crawler ID, or pass explicit URLs for surgical priority warming after a partial publish.
How it works
- 1
Copy the webhook URL
Use the platform-specific path from Deploy integrations.
- 2
Add API key headers
Send X-Public-Key and X-Secret-Key.
- 3
Ship with confidence
Confirm warmers run after the next deploy.
Where it shines
Storefront publishes
Trigger after Shopify theme or content changes.
Custom pipelines
Call the public webhook from any CI job.
Frequently asked questions
- Where do I find examples?
- Your account Deploy integrations page includes curl examples for Vercel, Netlify, and Shopify.
- Is this the same as CDN purge?
- No. Deploy triggers start warming; CDN integrations optionally purge then rewarm. Many teams use both.
Related features
All featuresReady to try this in your account?
Create a free Cache Rocket account, verify a hostname, and turn this capability on for your site or API.