DEVOPS
Dropbox Artifact Prune With Slack Approval
Weekly, builds a proposed deletion list of stale Dropbox artifacts and an AI-written rationale, posts it to Slack for a human approve/reject decision.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionList Dropbox artifacts and compute deletion candidatesDropbox
- ActionDraft prune rationale with OpenAIOpenAI
- LogicPost proposal to Slack and await approve/rejectSlack
- ActionDelete approved candidates from DropboxDropbox
- OutputPost final outcome and reclaimed space to SlackSlack
What it does
Adds a human gate to artifact cleanup. Each week it computes which Dropbox artifacts are safe to delete under your retention rules, uses an LLM to draft a plain-English rationale (what's going, why it's safe, what stays restorable), and posts the proposal to Slack. Deletion runs only after an approver clicks approve; a reject cancels the run and logs the decision.
When to use it
Use it when artifact storage matters but your team isn't comfortable with fully automated deletion. It gives you the convenience of an automated proposal with the safety of explicit human approval on every prune.
How it works
- 1A weekly schedule fires the run.
- 2List Dropbox artifacts and apply retention rules to compute a candidate deletion set, preserving the latest release per channel.
- 3Ask OpenAI to write a concise rationale summarizing the proposal and confirming restorability is intact.
- 4Post the proposal to Slack with approve/reject controls and wait for a decision.
- 5Branch: on approve, delete the candidate set from Dropbox; on reject, cancel and log.
- 6Post the final outcome and reclaimed space back to the Slack thread.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect OpenAIModels, embeddings, files.
- 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.