SECOPS
Stale Public-Link Aging and Cleanup Proposer
Finds Dropbox and Drive public links that have gone untouched past an age threshold, drafts a batched cleanup proposal in Linear.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled stale-link aging scan
- ActionGather links and timestamps from Dropbox and DriveDropbox
- LogicKeep links older than stale threshold
- LogicGroup stale links by owner
- ActionCreate batched cleanup issue per owner in LinearLinear
- OutputNotify owners with grace window in SlackSlack
What it does
Targets the long tail of forgotten public links — files shared months ago and never revisited. It identifies links whose last-access or share date is older than your threshold, groups them by owner, and produces a single batched cleanup proposal in Linear plus a courtesy Slack notice to each owner, giving people a grace window to object before links are torn down.
When to use it
Use this for periodic hygiene rather than incident response. It is the cleanup companion to real-time auditing: great for quarterly access reviews where the goal is to shrink the standing pool of public links without surprising anyone.
How it works
- 1A schedule triggers the aging scan on your review cadence.
- 2The flow gathers public links and their share/access timestamps from Dropbox and Drive.
- 3A logic step keeps only links older than the configured stale threshold.
- 4Stale links are grouped by owning user into batches.
- 5A single Linear issue per owner is created listing their stale links and the proposed removal date.
- 6Each owner gets a Slack notice with the grace window and an opt-out path.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect Google DriveDocs, sheets, slides, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Page on-call when a WAF rule mass-blocks legitimate traffic
On demand or every few minutes, it detects a single Cloudflare WAF rule suddenly blocking a broad spread of ASNs and paths (a likely false-positive storm).
PII Content Scan on New Dropbox External Share
When a file gets an external Dropbox link, it reads the file content, uses an AI classifier to detect PII or secrets.
Compile a weekly WAF tuning review with trends to Confluence
Every week an agent rolls up Cloudflare WAF block clusters by rule and ASN, compares them to prior weeks for trend direction.
Sensitive Dropbox Link Owner Remediation Loop
When a newly created Dropbox shared link points to a sensitive file, this workflow DMs the file owner, gives them a deadline to justify or revoke it.
GitLab Push Secret Detection to Block and History Purge
On a GitLab push that contains a detected secret, it revokes the exposed credential, opens a tracking issue with git-history purge instructions.
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.