Monitor server files for unauthorized changes and get alerted

Checks your important server files on a schedule and sends a Slack alert the moment one changes unexpectedly.

How the work actually flows

It branches. Exactly one path is taken; runs once per each watched file.

Pattern: Exclusive Choice (4) · Multiple Instances without Synchronization (12)

flowchart TD trig(["scheduled integrity check"]):::trigtime s0["connect to server"]:::task s1[["calculate file checksum"]]:::mi s2["compare to known checksum"]:::task trig --> s0 s0 -->|"one per each watched file"| s1 s1 --> s2 gx{"× did the file change"}:::gate s2 --> gx p00["send slack alert with details"]:::task gx -->|"file changed"| p00 p10["end quietly"]:::task gx -->|"no change"| p10 p00 --> out p10 --> out out[/"alert on unexpected file change"/]:::out pay{{"catch tampering immediately"}}:::pay out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepRuns once per itemOne path onlyResultPayoff
Build size
Standard

A mid-size build with several tools working together.

Business functions
Messaging & Notifications
Connects
Slack

The problem it solves

You have no way of knowing if someone tampers with a critical file on your server until something breaks or a customer reports a problem. Checking file integrity by hand is easy to forget and impossible to keep up daily.

Who it fits

IT teams or business owners running their own servers who need to know immediately if a critical file is altered.

How it works

  1. On a set schedule, the workflow checks your server over SSH
  2. It calculates a checksum for each file you're watching
  3. It compares the checksum against the known-good version
  4. If a file has changed, a Slack alert is sent with the details
  5. If nothing changed, the workflow ends quietly
What you get

Unauthorized file changes caught the moment they happen

You get an instant alert the second one of your critical server files changes unexpectedly.

What you get

A Slack alert the moment a monitored file changes unexpectedly, with details of what changed.

What you need

A server with SSH access and a Slack workspace.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook