DEVOPS
Dropbox Artifact Retention Review with Approval Gate
Monthly, an agent compiles a deletion candidate list of stale Dropbox artifacts, posts it to Slack for human approval, and only prunes the files an operator explicitly approves.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly review schedule fires
- ActionList artifacts and release tagsDropbox
- LogicBuild candidate list with justifications
- ActionPost proposal to Slack for approvalSlack
- LogicRoute only approved items forward
- ActionDelete approved artifactsDropbox
- OutputPost audit confirmation to SlackSlack
What it does
Once a month an agent reviews the Dropbox build-artifacts folder, cross-references GitHub release tags, and assembles a proposed deletion list with reasons and reclaimable size per file. Instead of acting on its own it posts the list to Slack with an approval prompt, then prunes only the items an operator confirms. The agent records the outcome for the audit trail.
When to use it
Use it when retention can't be fully automated — for example regulated builds or shared artifacts where a human must sign off before anything is deleted. It keeps a person in the loop while still doing all the tedious analysis.
How it works
- 1A monthly schedule starts the review.
- 2The agent lists Dropbox artifacts and gathers live GitHub release tags.
- 3It reasons over age and release linkage to build a candidate list with justifications.
- 4It posts the proposed deletions to Slack and waits for approval.
- 5A branch routes only the approved items forward.
- 6Delete the approved artifacts from Dropbox.
- 7Post a confirmation summary with the audit record 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
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.