SECOPS
Discord Webhook Abuse Anomaly Alert
On a webhook-event trigger, watches for abnormal posting through your Discord webhooks (spikes, off-hours bursts.
How it runs
The automated pipeline, trigger to output.
- TriggerDiscord webhook post receivedHTTP webhook
- ActionLoad webhook history and baseline from PostgresPostgres
- LogicScore event for anomaly vs baseline
- ActionRecord event to update baseline in PostgresPostgres
- OutputAlert security channel in Slack if anomalousSlack
What it does
Watches the traffic flowing through your Discord webhooks in real time. When a webhook starts firing far more often than its baseline, posts during unusual hours, or carries content patterns typical of spam takeovers, the flow treats the webhook as likely compromised and alerts your security team.
When to use it
Use it when legitimate webhooks (CI, alerts, bots) post to Discord on predictable cadences and a sudden flood means the token leaked. This catches abuse the moment it starts rather than after members report spam.
How it works
- 1An incoming webhook event delivers each Discord webhook post to the flow.
- 2A Postgres lookup pulls the recent send history and learned baseline for that webhook ID.
- 3A logic step scores the event against baseline — rate spike, off-hours timing, or suspicious payload — and decides if it crosses the anomaly threshold.
- 4Below threshold, the event is just recorded back to Postgres to update the baseline.
- 5Above threshold, a Slack alert goes to the security channel with the webhook ID, the trigger reason, and a one-click revoke link.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.