DEVOPS
Dropbox Build-Artifact Retention Governor
Runs on a schedule to scan a Dropbox build-artifacts folder, identify superseded builds beyond your retention policy.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionList Dropbox artifacts folder recursivelyDropbox
- LogicGroup by channel, rank, mark latest as protected
- LogicSkip channels whose latest artifact is missing
- ActionDelete superseded artifacts beyond retention countDropbox
- OutputPost kept/deleted/reclaimed summary to SlackSlack
What it does
Keeps a Dropbox build-artifacts folder from growing without bound. On a nightly schedule it inventories every artifact, groups them by release channel, keeps the N most recent per channel plus anything tagged as a current release, and deletes the rest. Before any deletion it verifies the latest release artifact is present so the prune never strands a channel without a restorable build.
When to use it
Use it when your CI uploads build outputs to Dropbox and storage keeps creeping up, but you can't just delete by age because some old builds are pinned production releases. It enforces a per-channel retention count safely and reports the reclaimed space.
How it works
- 1A nightly schedule fires the run.
- 2List the Dropbox artifacts folder recursively and collect file metadata (path, size, modified time, channel prefix).
- 3Group by channel and rank by modified time; mark the newest per channel as protected.
- 4Branch: if any channel's protected/latest artifact is missing, skip pruning that channel and flag it.
- 5Delete the superseded artifacts that fall outside the retention count.
- 6Post a Slack summary listing kept builds, deleted builds, reclaimed bytes, and any flagged channels.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 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
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.