Remote Flow Monitor

The problem

A recurring control required checking several remote folders and understanding whether files were waiting, already processed or absent. Running commands manually was possible, but the procedure depended on remembering paths, repeating the same checks and interpreting raw output each time.

The objective was to keep the operation strictly read-only while making the result easier to repeat, compare and hand over to another person.

The approach

Excel remains the control surface. A small configuration file defines the connection and base path; VBA launches SSH commands; the returned directory listings are normalised into a table with explicit outcomes such as OK, EMPTY or error.

Paths are derived from a compact configuration rather than embedded throughout the code. This reduces maintenance and makes the logic easier to audit.

How it works

• The user selects or refreshes the flow types to inspect.
• VBA builds the expected remote paths.
• SSH runs read-only directory commands.
• The output is parsed into file counts and outcomes.
• A single table keeps flow type, subfolder, remote path, file count and diagnostic message together.

Result

The control becomes less dependent on the operator. Instead of several terminal checks, the user gets one structured view and can immediately distinguish an empty folder from a connection problem or a folder containing work to investigate.

What I learned

Automation does not have to mean write access. Read-only automation can already remove a large amount of repetitive work, especially when the real value is consistency, traceability and reducing the number of details the operator must remember.

Stack: Excel · VBA · SSH · Windows