Automation library · Integrations

Guard Hostinger VPS CPU spikes with Anthropic and SSH

Started by a clock, and works across Email. 39 steps, 5 branches, 1 loop or waits: large, and worth reading before you trust it with anything live.

Large

Download free
39 stepsLarge: read it before trusting it with anything live
5Branches: places the flow splits
1Loop or waits
1Service it connects to

The flow

Starts it 1Model 1Logic 21Service 16

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

  1. 1IMAP Trigger: New ReplyEmail Read ImapService
  2. 2Schedule: Every 15 MinSchedule triggerStarts it
  3. 3Extract Case ID & DecisionCodeLogic
  4. 4Config: Detection SettingsSetLogic
  5. 5Case ID Found & Approved?IfLogic
  6. 6Get VPS MetricsHostinger ApiService
  7. 7Config (Kill Listener)SetLogic
  8. 8No Action (Not Approved)No OpLogic
  9. 9Analyze MetricsCodeLogic
  10. 10SSH: Read Case logSshService
  11. 11CPU Spike?IfLogic
  12. 12Parse CaseCodeLogic
  13. 13Get CPU Process ListSshService
  14. 14No Action: Below ThresholdNo OpLogic
  15. 15Found & Pending?IfLogic
  16. 16Format Process ListCodeLogic
  17. 17Create SnapshotHostinger ApiService
  18. 18Email: Case Not FoundEmail SendService
  19. 19Analyze CPU Spike with AIAnthropicModel
  20. 20Wait (snapshot buffer)WaitLogic
  21. 21Parse AI AnalysisCodeLogic
  22. 22Build Kill CommandCodeLogic
  23. 23Traffic-Driven?IfLogic
  24. 24SSH: Kill flagged processesSshService
  25. 25List FirewallsHostinger ApiService
  26. 26Build Log EntryCodeLogic
  27. 27Build Kill Log EntryCodeLogic
  28. 28Find Lockdown FirewallCodeLogic
  29. 29Log CPU useSshService
  30. 30SSH: Log case (killed)SshService
  31. 31Lockdown Firewall Exists?IfLogic
  32. 32Alert: Non-Traffic CPU SpikeEmail SendService
  33. 33Email: Killed ConfirmationEmail SendService
  34. 34Activate Lockdown FirewallHostinger ApiService
  35. 35Create Lockdown FirewallHostinger ApiService
  36. 36Alert: Lockdown ActivatedEmail SendService
  37. 37Split Allowed PortsCodeLogic
  38. 38Create Firewall RuleHostinger ApiService
  39. 39Finalize Lockdown FirewallCodeLogic

How it's built

Starts on
A clock
Steps
39, with 5 branches, 1 loop or waits
Size
Large: read it before trusting it with anything live
Connects to
Email
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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

What starts it?

It starts on a clock.

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?

Take your time. At 39 steps it is large: read it before trusting it with anything live.

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 39 steps before you point it at anything that matters.