SECOPS
Reporter Feedback Loop & Case Closeout
When a phishing case verdict is finalized in Postgres, automatically replies to the original reporter with a plain-language outcome, updates a leaderboard of top reporters.
How it runs
The automated pipeline, trigger to output.
- TriggerCase verdict finalized in triage tablePostgres
- LogicMap verdict to plain-language outcome
- ActionReply to original reporter with outcomeGmail
- ActionUpdate top-reporter leaderboardPostgres
- OutputResolve originating ticket in queueZendesk
What it does
Closes the loop with the human who reported the email. As soon as a case reaches a final verdict, it sends the reporter a clear thank-you with what was found and what action was taken, credits them on a reporting leaderboard to reinforce good behavior, and marks the originating ticket resolved.
When to use it
When you want to keep employees reporting suspicious mail by acknowledging every submission, and to retire closed cases automatically instead of leaving stale tickets open in your queue.
How it works
- 1A row in the Postgres triage table flips to a finalized verdict, firing the trigger.
- 2A logic step maps the verdict to a friendly outcome message (confirmed phishing, safe, or already handled).
- 3The flow emails the original reporter via Gmail with the outcome and any guidance.
- 4The reporter's running tally is updated on the recognition leaderboard in Postgres.
- 5The originating case is transitioned to resolved in the Zendesk ticket queue.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GmailRead, draft, send, label.
- 3Connect ZendeskTickets, queues, knowledge base.
- 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.