DEVOPS
Weekly Stale-Preview Audit That Files Linear Cleanup Tickets
Weekly, audits all Vercel preview deployments against TTL and ownership rules, opens a Linear ticket per stale preview assigned to its owner.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionList all preview deploymentsVercel
- LogicFlag policy violations + resolve ownerGitHub
- ActionOpen Linear ticket per stale previewLinear
- ActionArchive audit snapshot to PostgresPostgres
- OutputRoll-up of tickets + stale count
What it does
Runs a governance-style weekly audit of every preview deployment, turning each policy violation into a tracked Linear ticket assigned to the responsible engineer. It does not delete anything itself; it makes cleanup accountable and visible.
When to use it
When your org prefers owner-driven cleanup over automated deletion, or needs an auditable paper trail of stale environments for compliance. Pairs well with teams that already live in Linear.
How it works
- 1A weekly schedule kicks off the audit.
- 2List all Vercel preview deployments with age, branch, and last-activity data.
- 3Logic flags each preview that violates TTL or ownership policy and resolves the owner from GitHub commit history.
- 4For every flagged preview without an existing open ticket, create a Linear issue assigned to the owner describing the preview and recommended action.
- 5Write the complete audit snapshot — flagged and clean — to Postgres for historical reporting.
- 6Output a roll-up of tickets created and total stale previews for the week.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect PostgresAny Postgres URL — query, write, migrate.
- 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.