DEVOPS
Vercel Preview TTL Reaper with Slack Owner Confirmation
Finds Vercel preview deployments older than their TTL, pings each deployment's git author in Slack for keep-or-delete confirmation, and deletes the ones nobody saves.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionList Vercel preview deployments + authorsVercel
- LogicKeep only preview deploys past TTL
- ActionDM author for Keep/Delete confirmationSlack
- LogicBranch on response or grace timeout
- ActionDelete unsaved deploymentsVercel
- OutputPost reclaimed-environment summary to channelSlack
What it does
Sweeps your Vercel project for preview deployments that have outlived their time-to-live, identifies the engineer who pushed each one, and asks them in Slack whether to keep it. Anything not explicitly saved within the grace window is deleted, reclaiming build minutes and bandwidth.
When to use it
Run it nightly when feature-branch previews pile up after merges. Ideal for teams on Vercel where stale `preview` deployments accumulate and you want owners to make the call rather than blanket-deleting.
How it works
- 1A daily schedule fires the run.
- 2List all Vercel deployments for the target project and read each one's created timestamp and git author.
- 3A filter keeps only `preview` deployments older than the TTL (e.g. 7 days) that aren't aliased to a live URL.
- 4For each survivor, send the git author a Slack DM with Keep / Delete buttons and a 24h grace note.
- 5A branch routes the response: Keep tags the deployment as protected; Delete (or no reply) proceeds.
- 6Delete the unsaved deployments via the Vercel API and post a summary of reclaimed environments to the team channel.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
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.
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…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.