DEVOPS
Dropbox CI Artifact Retention Sweeper
On a nightly schedule, scans a Dropbox build-artifacts folder, deletes files older than the retention window unless they back a live GitHub release tag.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionList Dropbox artifacts folderDropbox
- LogicKeep files older than retention window
- ActionFetch live GitHub release tagsGitHub
- LogicSpare artifacts backing a live release
- ActionDelete stale artifacts from DropboxDropbox
- OutputPost deletion report to SlackSlack
What it does
Each night this workflow walks your Dropbox build-artifacts folder, finds every file past the retention window, and checks each candidate against your live GitHub release tags before deleting. Artifacts that still back a published release are spared; everything else stale is pruned. A summary of what was kept, deleted, and reclaimed lands in Slack.
When to use it
Use it when CI dumps build outputs to Dropbox and the folder grows without bound. It enforces a clear retention policy automatically while guaranteeing you never delete an artifact a current release still depends on.
How it works
- 1A nightly schedule fires the sweep.
- 2List the Dropbox artifacts folder with file paths, sizes, and modified dates.
- 3A filter keeps only files older than the retention window (e.g. 30 days).
- 4Fetch current GitHub release tags and match each stale file against the set.
- 5A branch spares any artifact tied to a live release; the rest are marked for deletion.
- 6Delete the marked files from Dropbox.
- 7Post a Slack report listing deleted count, spared count, and bytes reclaimed.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.