SECOPS
Live Secret Exposure to PagerDuty Incident Escalation
Detects high-severity secrets (cloud root keys, payment tokens) in a push and escalates straight to PagerDuty as a critical incident, with a Linear evidence ticket linked.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub push event receivedGitHub
- LogicClassify detected secret by blast radius severity
- ActionTrigger critical PagerDuty incident for on-callPagerDuty
- OutputOpen linked Linear evidence ticketLinear
What it does
This workflow distinguishes ordinary secret leaks from catastrophic ones. When a push contains a high-blast-radius credential such as an AWS root key or a Stripe live key, it pages on-call through PagerDuty rather than just filing a ticket, because those keys can drain accounts in minutes.
When to use it
Use it for repos that can touch production infrastructure or money movement. It is the escalation path for the secrets you cannot afford to let sit in a backlog overnight.
How it works
- 1A GitHub push event triggers the workflow.
- 2A logic step classifies any detected secret by blast radius using a severity ruleset.
- 3If severity is low or nothing is found, the run exits without paging.
- 4If severity is critical, an action triggers a PagerDuty incident with the repo, commit, and key type in the payload.
- 5A linked Linear ticket is opened as the evidence record so the page and the audit trail stay connected after the incident closes.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect LinearIssues, projects, cycles, triage.
- 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
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.