SECOPS
Third-Party Token Leak Vendor Disclosure Notifier
When a push exposes a third-party vendor token (Stripe, Datadog, etc.), it notifies the vendor's revocation endpoint via webhook, alerts your team in MS Teams.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub push event receivedGitHub
- LogicIdentify issuing vendor from token format
- ActionCall vendor revocation endpoint via webhookHTTP webhook
- ActionAlert security channel in MS TeamsMicrosoft Teams
- OutputOpen Linear disclosure tracking ticketLinear
What it does
Some leaked secrets belong to outside vendors, and the fastest revocation path is the vendor's own token-revocation endpoint. This workflow detects a third-party token in a push, calls the matching vendor revocation webhook, alerts your team, and tracks the disclosure to closure.
When to use it
Use it when your code embeds partner credentials whose rotation you do not fully control internally. It ensures the issuing vendor is notified to kill the token, not just your own systems, and keeps a record of whether they confirmed.
How it works
- 1A GitHub push event triggers the workflow.
- 2A logic step identifies the vendor that issued the detected token from its prefix and format.
- 3An HTTP webhook call hits that vendor's revocation or disclosure endpoint with the leaked fingerprint.
- 4An action posts an MS Teams alert to the security channel with the repo, vendor, and revocation status.
- 5A Linear disclosure ticket is opened to track vendor acknowledgment through to confirmed revocation as the final output.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect Microsoft TeamsChannels, chats, files.
- 4Connect LinearIssues, projects, cycles, triage.
- 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
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
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.
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.