DEVOPS
Dropbox Orphan-Artifact Reaper
Cross-references Dropbox artifacts against open GitHub branches and tags, flags artifacts whose source branch was deleted or merged long ago.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires
- ActionList Dropbox artifacts and parse source refsDropbox
- ActionQuery GitHub for live branches and tagsGitHub
- LogicClassify artifacts as orphan vs protected
- ActionDelete orphan artifacts from DropboxDropbox
- OutputPost reaped list and reclaimed space to SlackSlack
What it does
Finds and removes build artifacts in Dropbox that no longer map to anything alive in GitHub. It lists every artifact, extracts the branch or tag each was built from, and checks whether that ref still exists. Artifacts from deleted or long-merged branches are reaped; artifacts tied to existing tags or the latest release are always protected.
When to use it
Use it when feature-branch CI dumps per-branch artifacts into Dropbox and they pile up after branches merge or get deleted. This reclaims space tied to dead refs without risking anything that backs a real release.
How it works
- 1A schedule fires the run.
- 2List Dropbox artifacts and parse the source ref from each artifact's name or metadata.
- 3Query GitHub for current branches and tags.
- 4Branch: classify each artifact as orphan (ref gone) or protected (ref or release still exists).
- 5Delete the orphan artifacts from Dropbox.
- 6Post the reaped list, retained count, and reclaimed space to Slack.
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
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.