SECOPS

Sync the public Dropbox link inventory for Cloudflare correlation

On a schedule, enumerates every public Dropbox share link and writes a current inventory to Axiom so downstream Cloudflare log correlation always matches against fresh.

CategorySecOps
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled inventory refresh fires
  • ActionList all active public Dropbox shared linksDropboxDropbox
  • LogicDiff against last snapshot for added/removed/changed links
  • ActionWrite normalized inventory to Axiom datasetAxiom
  • OutputPost additions and removals summary to SlackSlack

What it does

Keeps the source-of-truth inventory of public Dropbox share links current. It lists all active shared links, normalizes their IDs and target paths, and pushes the inventory into Axiom where the geo-anomaly detection workflow joins against it.

When to use it

Use this as the foundation under any Cloudflare-vs-Dropbox correlation. Detection is only as good as the link inventory it joins against; stale inventory means missed or misattributed hits. Schedule it hourly or daily depending on how often your team creates new shares.

How it works

  1. 1A scheduled timer fires at the configured interval.
  2. 2Dropbox returns every active public shared link with its path, visibility, and expiry.
  3. 3A logic step diffs the result against the last snapshot to find added, removed, and changed links.
  4. 4The normalized inventory is written to an Axiom dataset keyed by link ID.
  5. 5A summary of additions and removals is posted to Slack so owners can spot links they didn't expect.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DropboxFiles and folders.
  2. 2
    Connect AxiomLog streams, queries, dashboards.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.