diditarrive
Sign inSign up

Use case

The vendor drops the file. Nobody notices the day they do not.

A supplier writes a sales CSV into a folder on an SFTP server every weekday morning, and three reports downstream are built from it.

How it fails today

The job on their side fails, or a filename changes, or the disk fills. The folder simply stays as it was, and nothing on your side has an opinion about a file that is not there.

10:00The first person to notice is whoever reads the report.

What we do about it

A weekday, as we would run it
  1. from 05:00We list the folder through the window and look for a new match.
  2. 07:00Due passes with nothing new. Late, and no alert yet.
  3. 07:20Grace ends. One alert, naming the folder and the last file we did see.
  4. 08:04The re-send lands. One closing alert.

What we need

A host, a folder and a user that can list it. Read-only is plenty, and we pin the host key on the first connection. The full posture.

one folderlistings, not contentshost key pinned
The monitor, configured

Daily sales export

Where
SFTP, /inbound
Match
sales_*.csv
When
weekdays by 07:00
Grace
20 minutes

If the key expires, that’s Check broken, never Missed - broken access is its own alert, and it says whose job it is to fix.

Set it up in a sentence:

“The supplier drops a sales CSV in /inbound every weekday by 7am, give it 20 minutes.”

Create monitor
Same shape, different plumbing:The connectorsThe schedule modelPricing
Menu
ProductUse CasesConnectorsPricingTrustSign inSign up