Monitor remote server file integrity with SSH and Slack alerts
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Cron. 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 6 nodes and runs on a schedule (legacy Cron node). Along the way it connects Slack.
How it runs
Trigger: On a schedule (legacy Cron node).
- List Files & Checksums (Code): runs custom JavaScript code
- Get Remote File Checksum (SSH): uses SSH
- Checksums Match? (If): checks a condition and branches into true / false
- Send Alert (Slack): uses Slack
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Cron in Scheduled Check: replace with Schedule Trigger.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Cron Scheduled Check | Schedule Trigger |
Nodes used (6)
- Cron
n8n-nodes-base.cron - Code
n8n-nodes-base.code - SSH
n8n-nodes-base.ssh - If
n8n-nodes-base.if - No Operation, do nothing
n8n-nodes-base.noOp - Slack
n8n-nodes-base.slack
From the author
--- How It Works: The 5-Node Security Flow This workflow efficiently performs a scheduled file integrity audit. 1. Scheduled Check (Cron Node) This is the workflow's trigger. It schedules the workflow to run at a specific, regular interval. Function:…