IT OPS

Agent-driven cleanup of stale Dropbox shares older than a policy threshold

An agent reviews shared links and external grants that have had no access activity past your aging policy, decides keep/expire/revoke per item using folder context.

CategoryIT Ops
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonthly schedule starts aging review
  • ActionList links and grants with last-access dataDropboxDropbox
  • LogicNarrow to items past aging threshold
  • ActionAgent decides keep/expire/revoke per item
  • ActionApply expiries and revocations in DropboxDropboxDropbox
  • OutputLog decisions and rationale to CodaCodaCoda

What it does

This agent-driven workflow finds Dropbox shared links and external grants that have gone untouched longer than your aging policy (for example 90 days with zero access). For each one it weighs folder sensitivity, link audience, and last-access date to decide whether to keep, set an expiry, or revoke outright, then applies the decision and records its reasoning.

When to use it

Use it when blunt rules over-revoke and you want judgment: a link to an active project folder shouldn't die just because it was quiet for a month, but a public link to an archived folder should. The agent applies nuanced policy at scale.

How it works

  1. 1A monthly schedule starts the aging review.
  2. 2Dropbox returns links and grants with last-access metadata.
  3. 3A filter narrows to items past the aging threshold.
  4. 4The agent evaluates each item against folder context and policy, choosing keep, expire, or revoke.
  5. 5Dropbox applies expiries and revocations per decision.
  6. 6The agent writes each item, decision, and rationale to a Coda log for review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DropboxFiles and folders.
  2. 2
    Connect CodaDocs, packs, automations.
  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.