SECOPS
Loom leak auto-unshare with owner remediation coaching
On a confirmed secret in a Loom video, immediately restricts the recording's sharing to stop further exposure, then DMs the owner a clear remediation checklist.
How it runs
The automated pipeline, trigger to output.
- TriggerLoom recording publishedLoom
- ActionScan transcript and frames for secretsOpenAI
- LogicProceed only on confirmed live secret
- ActionRestrict Loom recording sharingLoom
- OutputDM owner a remediation checklistSlack
What it does
This workflow focuses on the human side of a leak. The instant a published Loom recording is found to contain a live credential, it flips the recording's sharing setting to restricted so no new viewers can see the secret, then reaches the person who recorded it with a direct, specific message about what leaked and exactly what to do next.
When to use it
Reach for this when your priority is containment plus education rather than infrastructure revocation, for example secrets you can't programmatically revoke (third-party dashboards, customer URLs). It pairs well with a separate revocation flow and turns each leak into a teachable moment.
How it works
- 1A Loom webhook fires on a published recording.
- 2The recording's transcript and frame text are fetched and scanned for credentials.
- 3A logic branch proceeds only when a secret is confirmed live.
- 4The flow updates the Loom recording's sharing to restricted, halting new views.
- 5It looks up the recording owner's email and resolves their Slack user.
- 6A direct Slack message delivers a remediation checklist: rotate the key, confirm rotation, re-record without the secret on screen.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect OpenAIModels, embeddings, files.
- 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 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.