DEVOPS
Orphaned Dropbox Artifact Reconciler on Release Delete
When a GitHub release is deleted, finds the Dropbox artifacts that backed it, confirms no other live tag references them.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub release deletedGitHub
- LogicResolve tag to artifact paths
- ActionList remaining live releasesGitHub
- LogicKeep artifacts referenced by no release
- ActionMove orphans to Dropbox quarantineDropbox
- OutputPost quarantine note to SlackSlack
What it does
When someone deletes a GitHub release, the build artifacts it pointed to are usually left behind in Dropbox as orphans. This workflow reacts to the release-deletion event, locates the matching artifacts, double-checks they aren't shared by any other live release, and moves the orphans into a dated quarantine folder instead of deleting outright.
When to use it
Use it when releases get pulled or superseded and you want their artifacts cleaned up promptly without risking data loss. Quarantine gives a recovery window before a later sweep removes them for good.
How it works
- 1A GitHub release-deleted event triggers the flow.
- 2Resolve the deleted tag to its expected Dropbox artifact paths.
- 3List the live GitHub releases to build a still-referenced set.
- 4A branch keeps only artifacts referenced by no remaining release.
- 5Move those orphaned files into a dated Dropbox quarantine folder.
- 6Post a Slack note naming the deleted release and the quarantined files.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect DropboxFiles and folders.
- 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.