DEVOPS
Verify edge freshness after purge and roll back Vercel if stale
After purging Cloudflare on a production deploy, probes the live edge for the new build hash and, if the edge still serves the old build past a retry window, rolls the Vercel…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel production deploy succeededVercel
- ActionCloudflare purge_everythingCloudflare
- ActionProbe live edge for new build hashShell
- LogicBranch on stale vs fresh after retries
- ActionPromote previous Vercel deploy (rollback)Vercel
- OutputPage on-call via PagerDutyPagerDuty
What it does
This is a self-healing release guard. After a Vercel production deploy, it purges Cloudflare and then actively probes the public edge to confirm it is serving the new build. If the edge keeps returning the old build fingerprint after several retries, it promotes the previous Vercel deployment back to production and escalates to PagerDuty.
When to use it
Use it for revenue-critical apps where a deploy that silently fails to propagate is worse than a delayed deploy. It turns a stuck cache into an automated rollback instead of a 2 a.m. manual investigation.
How it works
- 1Vercel `deployment.succeeded` for production triggers the run.
- 2Cloudflare purge_everything clears the zone.
- 3A shell step curls the live URL repeatedly, checking the response for the expected build hash.
- 4A logic branch decides: hash matches means done; still stale after the retry budget means degraded.
- 5On failure, Vercel promotes the prior deployment back to production.
- 6PagerDuty receives an incident with the probe evidence and rollback target.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect ShellRun sandboxed commands inside the workspace.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.