SECOPS

Daily Phishing Trend Digest

Runs each morning to summarize the prior day's phishing reports, highlights repeat sender domains and spikes.

CategorySecOps
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled weekday-morning run
  • ActionQuery prior 24h of phishing casesPostgreSQLPostgres
  • ActionAggregate verdicts, domains, and targets
  • LogicFlag volume spike vs rolling baseline
  • OutputPost trend digest to leadership SlackSlack

What it does

Gives security leadership a daily pulse on phishing activity. It aggregates the previous day's cases from the case store, surfaces the top targeted users, repeat malicious domains, and verdict breakdown, and flags any sudden volume spike that suggests an active campaign.

When to use it

Use this when individual reports are handled well but no one sees the bigger picture. Useful for managers and threat analysts who need to spot coordinated campaigns and report metrics without building dashboards by hand.

How it works

  1. 1A scheduled trigger fires every weekday morning.
  2. 2The workflow queries the phishing case table in Postgres for the prior 24 hours of reports.
  3. 3An aggregation step computes counts by verdict, top sender domains, most-targeted recipients, and day-over-day change.
  4. 4A branch flags a spike when volume exceeds the rolling baseline, adding a prominent alert line.
  5. 5The formatted digest is posted to the leadership Slack channel with the spike flag and key numbers.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.