DEVOPS
Staging Environment Registry Reaper with Owner Email Poll
Reads a registry of long-lived staging environments from Airtable, emails each owner about ones past their expiry date.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery Airtable for expired env rowsAirtable
- ActionEmail owner: extend or releaseGmail
- LogicBranch on extension reply vs deadline
- ActionMark unanswered rows pending-decommissionAirtable
- OutputPost decommission digest to ops channelSlack
What it does
Treats an Airtable table as the source of truth for named staging environments (each with an owner, purpose, and expiry date). It finds rows past expiry, emails the owner asking to extend or release, and flips unanswered rows to a decommission state so an operator can reclaim them.
When to use it
Use when staging environments are manually provisioned and tracked in a spreadsheet rather than spun up per-branch. Good for shared QA or demo stacks where the cost of forgetting is real and ownership must be respected.
How it works
- 1A weekly schedule starts the run.
- 2Query Airtable for environment rows where `expiry_date` is in the past and `status` is active.
- 3For each expired row, email the owner with extend-or-release instructions and a deadline.
- 4A branch checks the owner's reply or the deadline: an extension reply pushes the expiry date forward in Airtable.
- 5Rows with no extension are set to `pending-decommission` in Airtable.
- 6Post a digest of pending-decommission environments to the ops Slack channel for action.
Set it up
What you configure once, before turning it on.
- 1Connect AirtableBases, tables, views, automations.
- 2Connect GmailRead, draft, send, label.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.