SECOPS
Acknowledge Phishing Reporters and Close the Loop
After a reported email is triaged, this emails the employee who reported it with the outcome, awards a recognition note for true positives.
How it runs
The automated pipeline, trigger to output.
- TriggerTriage-complete webhook receivedHTTP webhook
- LogicSelect tone by verdict outcome
- ActionEmail acknowledgment to reporterGmail
- ActionAppend report to awareness scoreboardAirtable
- OutputShout out confirmed catches in channelSlack
What it does
Reinforces good reporting behavior. Once triage produces a verdict, the original reporter gets a clear, friendly reply telling them whether their report was a real threat, a false alarm, or marketing spam, and confirmed catches earn a recognition note. Reporter activity is logged for a security-awareness scoreboard.
When to use it
Use this when your phishing inbox is a black hole that never replies to reporters, eroding the habit you want to encourage. Closing the loop measurably increases future report rates.
How it works
- 1A triage-complete webhook arrives with the verdict and the reporter's address.
- 2A branch selects the right message tone for confirmed-threat, false-alarm, or spam outcomes.
- 3A personalized acknowledgment email is sent to the reporter via Gmail.
- 4The report, verdict, and reporter are appended to an Airtable scoreboard for awareness metrics.
- 5Confirmed true-positive catches post a shout-out to the team Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect GmailRead, draft, send, label.
- 3Connect AirtableBases, tables, views, automations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
Scheduled AWS Access-Key Age Sweep and Forced Rotation
Runs daily to find IAM access keys older than your policy threshold, deactivates the stale key, issues a fresh pair, and notifies the key owner with their replacement instructions.
Correlate Datadog WAF anomaly alert with Cloudflare evidence
When Datadog fires a WAF block-rate anomaly monitor, it pulls the matching Cloudflare firewall events, builds an evidence pack of top rules and ASNs.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
Non-Rotatable Leaked Secret to PagerDuty Escalation
Catches secret-scan hits for credentials that cannot be auto-rotated, gathers blast-radius context, and pages the on-call engineer with a step-by-step manual rotation runbook.
GitHub Secret-Scan Hit to Auto-Revoke and Rotate
When GitHub secret scanning flags a leaked credential in a repo, it auto-classifies the secret type, revokes the live key at the provider, mints a replacement.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
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.