SECOPS
Phishing Inbox URL Detonation & Verdict Routing
Watches the abuse@ mailbox for user-reported phishing, opens every embedded link in an isolated Browserbase session to capture redirects and screenshots.
How it runs
The automated pipeline, trigger to output.
- TriggerNew email in abuse@ mailboxGmail
- ActionExtract URLs and sender metadata from email
- ActionDetonate each URL in isolated browser sessionBrowserbase
- LogicScore redirects and assign clean/suspicious/malicious verdict
- ActionInsert case + evidence into triage tablePostgres
- OutputPage on-call only for malicious verdictsPagerDuty
What it does
Turns the shared phishing-report mailbox into an automated triage queue. Every reported email is parsed for URLs, each link is detonated in a throwaway cloud browser, and a structured verdict (clean / suspicious / malicious) is written to your case table. Confirmed-malicious reports escalate to on-call; everything else is quietly archived with evidence attached.
When to use it
When employees forward suspected phishing to a central address and your SOC is drowning in manual link-clicking. Ideal for teams that want every report adjudicated within minutes without an analyst risking their own machine on a live payload.
How it works
- 1A new message lands in the monitored Gmail abuse mailbox and fires the trigger.
- 2The flow extracts sender, subject, and all href targets from the raw email body.
- 3Each URL is opened in an isolated Browserbase session that records the final landing domain, redirect chain, and a full-page screenshot.
- 4A logic step scores the result against credential-harvest and lookalike heuristics to assign a verdict.
- 5The verdict, evidence URLs, and screenshot reference are inserted into a Postgres triage table.
- 6If the verdict is malicious, PagerDuty pages the on-call SOC analyst with the case link.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 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
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
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.
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.
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.