Automation library · Alerts and monitoring

Malicious file detection & response: Wazuh to VirusTotal

Started by another system calling it, and works across Gmail and Slack. 9 steps, 1 branch: a working afternoon to understand properly.

Medium

9 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 4Service 4

The steps in the order they run, from what starts it.

  1. 1Wazuh AlertWebhookStarts it
  2. 2Extract IOCsCodeLogic
  3. 3VirusTotal File Hash ValidationHttp RequestService
  4. 4Generate File SummaryCodeLogic
  5. 5file summary displayHtmlLogic
  6. 6Filter Suspicious FilesSwitchLogic
  7. 7Gmail1GmailService
  8. 8Slack File AlertSlackService
  9. 9Create File IncidentService NowService

How it's built

Starts on
Another system calling it
Steps
9, with 1 branch
Size
Medium: a working afternoon
Connects to
Gmail, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Gmail and Slack accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 9 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 9 steps before you point it at anything that matters.