IT OPS

Auto-revoke orphaned Dropbox shared links on a nightly drift sweep

Scans every team folder nightly for shared links pointing at deleted, moved, or expired files and automatically revokes the dead links, then emails IT a revocation summary.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule fires the sweep
  • ActionList all team folders and shared linksDropboxDropbox
  • ActionResolve each link target pathDropboxDropbox
  • LogicKeep only links with missing/moved targets
  • ActionRevoke orphaned shared linksDropboxDropbox
  • OutputEmail revocation digest to ITOutlook

What it does

Each night this workflow walks all Dropbox team folders, lists every active shared link, and checks whether each link's target still exists at the expected path. Links pointing at deleted or moved files (orphaned shares) are revoked automatically, and IT gets a single digest of everything that was cleaned up.

When to use it

Run it when shared links keep leaking access to content that was supposedly removed. Over months, files get deleted or relocated but their public/team links linger, leaving stale URLs that still resolve. This closes that gap without anyone manually auditing link lists.

How it works

  1. 1A nightly schedule fires the sweep.
  2. 2The flow pulls all team folders and their shared links from Dropbox.
  3. 3For each link, it resolves the target path and checks existence.
  4. 4A filter keeps only links whose target is missing or relocated.
  5. 5Each orphaned link is revoked via the Dropbox API.
  6. 6A run summary (links checked, revoked, skipped) is emailed to the IT distribution list through Outlook.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DropboxFiles and folders.
  2. 2
    Connect OutlookMail, calendar, contacts.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.