DEVOPS
Reclaim Idle Preview Deploys With No Recent Traffic
Each night queries preview-deployment access logs in Postgres, flags previews with zero traffic past an idle threshold, warns owners in Microsoft Teams.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionQuery idle previews from access logsPostgres
- LogicFilter previews idle past threshold
- ActionResolve owner from GitHub metadataGitHub
- ActionWarn owner in Teams + stamp deadlineMicrosoft Teams
- OutputDelete still-idle previews via VercelVercel
What it does
Retires preview deployments based on actual usage rather than calendar age. A preview that has served no requests for the idle threshold is treated as abandoned, its owner is warned, and it is deleted if it stays idle.
When to use it
When some long-lived previews are still in active use while others sit untouched, so a flat TTL would either kill useful environments or keep dead ones. Idle-based reaping targets exactly the abandoned ones.
How it works
- 1A nightly schedule starts the run.
- 2Query Postgres access-log aggregates for last-request timestamps per preview deployment.
- 3A filter selects previews idle longer than the threshold (e.g. 10 days of zero traffic).
- 4For each, resolve the owner from the GitHub deployment metadata.
- 5Post a warning in the owner's Microsoft Teams channel with the idle duration and deletion date, and stamp the grace deadline in Postgres.
- 6On a subsequent run, delete previews still idle past their deadline via the Vercel API and confirm reclaim in Teams.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect Microsoft TeamsChannels, chats, files.
- 4Connect VercelDeploys, runtime logs, analytics.
- 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
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.