SECOPS
Triage Outlook Phishing Reports with Slack Approval
Pulls reports from a shared Outlook phishing folder, auto-scores each one, and posts low-confidence cases to Slack with approve/dismiss buttons so an analyst makes the final call…
How it runs
The automated pipeline, trigger to output.
- TriggerNew report in Outlook phishing folderOutlook
- ActionScore report and assign confidenceOpenAI
- LogicBranch on confidence band
- OutputPost uncertain case with approve/dismiss buttonsSlack
What it does
Keeps a human in the loop for ambiguous reports. Messages from a shared Outlook phishing folder are scored automatically; clear-cut malicious and clearly-benign cases are handled silently, while anything in the uncertain middle is posted to Slack with action buttons for an analyst to decide.
When to use it
Use this when your team wants automation speed but isn't comfortable auto-purging on a model verdict alone. It is ideal for orgs on Microsoft 365 that route reports into a monitored mailbox folder.
How it works
- 1A new item in the shared Outlook phishing folder triggers the run.
- 2An OpenAI step scores the report and assigns a confidence band.
- 3A branch routes high-confidence verdicts straight to logging and low-confidence ones to human review.
- 4Uncertain cases post to Slack with Approve-purge and Dismiss buttons.
- 5The analyst's button click writes the final verdict back, closing the loop and feeding downstream remediation.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect OpenAIModels, embeddings, files.
- 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.