DEVOPS
Dropbox Quota Overflow Emergency Artifact Prune
When a webhook reports Dropbox usage crossing a quota threshold, prunes the oldest non-release artifacts until usage drops under target and pages on-call via PagerDuty if it can't.
How it runs
The automated pipeline, trigger to output.
- TriggerQuota-alert webhook receivedHTTP webhook
- ActionList Dropbox artifacts oldest firstDropbox
- ActionFetch live GitHub release tagsGitHub
- LogicDelete oldest unprotected until under target
- LogicCheck whether target reached
- OutputPage on-call or post all-clearPagerDuty
What it does
This workflow listens for a quota-alert webhook and reacts when Dropbox storage crosses a danger threshold. It pulls the artifact inventory, sorts oldest first, and deletes non-release files in order until projected usage falls back under the target. If it still can't free enough space, it pages on-call so a human steps in before builds start failing.
When to use it
Use it as a safety net when a full Dropbox would break your CI uploads. It's the reactive counterpart to a scheduled sweep — it only runs under pressure and prioritizes getting back under quota fast.
How it works
- 1A quota-alert webhook triggers the flow with current usage.
- 2List the Dropbox artifacts with sizes and dates, oldest first.
- 3Fetch live GitHub release tags to protect referenced artifacts.
- 4A loop deletes the oldest unprotected files until projected usage is under target.
- 5A branch checks whether the target was reached.
- 6If still over, page on-call through PagerDuty; otherwise post an all-clear to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect DropboxFiles and folders.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
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-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.