SECOPS
Discord Invite Link Leak Scanner
Scans the public web on a schedule for your Discord server's invite codes posted outside approved channels, and files a Linear ticket for each leaked or unauthorized invite found.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionList active invite codes from DiscordDiscord
- ActionSearch public web for each invite codeExa
- LogicFilter out allowlisted source domains
- OutputOpen a Linear issue per leaked inviteLinear
What it does
Finds places on the open web where your Discord invite links have been pasted — scraper sites, paste bins, low-quality 'free server' aggregators — that you never authorized. Each unexpected hit becomes a triaged Linear issue so your team can revoke the underlying invite code.
When to use it
Run this when you maintain a private or paid community and need to know the moment an invite that was meant for one person ends up broadcast publicly. Catching a leaked permanent invite early lets you revoke it before raiders or scrapers flood in.
How it works
- 1A daily schedule kicks off the run.
- 2The flow pulls your server's active invite codes from Discord so it knows exactly what to search for.
- 3A web search runs each invite code as a query against the public web.
- 4A logic step drops results that match your allowlisted domains (your own site, docs, approved partners).
- 5Remaining hits are unauthorized exposures; one Linear issue is opened per leaked code with the source URL and code attached.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect ExaNeural search across the web.
- 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
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.