SECOPS
Universal push webhook secret scanner with PagerDuty paging and Slack fan-out
Accepts push webhooks from any Git host, scans the payload for live secrets, and routes verified exposures to both PagerDuty for paging and a Slack incident channel…
How it runs
The automated pipeline, trigger to output.
- TriggerHTTP push webhook receivedHTTP webhook
- LogicNormalize payload and extract changed content
- LogicScan and keep only verified live secrets
- ActionOpen PagerDuty incident for on-callPagerDuty
- ActionPost exposure details to Slack channelSlack
- OutputReturn 200 with verified leak countHTTP webhook
What it does
This workflow exposes a generic HTTP webhook that any source control system can post push events to. It normalizes the payload, scans the changed content for credentials, verifies which detections are live, and on confirmation both opens a PagerDuty incident and posts to a Slack incident channel so paging and team coordination happen together.
When to use it
Use it when your code lives across multiple or self-hosted Git platforms that all support outbound webhooks, and you want one scanning pipeline feeding both your paging tool and your chat war room. Good for heterogeneous environments without native GitHub or GitLab app coverage.
How it works
- 1An HTTP webhook receives a push payload from any Git host.
- 2A logic step normalizes the payload and extracts changed file contents.
- 3A scan step matches credentials by pattern and entropy.
- 4A logic branch keeps only verified live secrets.
- 5A PagerDuty action opens an incident for the on-call rotation.
- 6A Slack action posts the same exposure details to the incident channel.
- 7The output returns a 200 with the count of verified leaks for the caller's logs.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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.