diditarrive
Sign inSign up

Use case

The report comes by email, and email is where things go quiet.

A partner emails a spreadsheet every Monday morning. There is no bucket, no API and no prospect of one, because the person sending it works in a mail client.

How it fails today

A rule files it, or it lands in junk, or the sender is on holiday. An inbox is very good at making an absence look like a quiet week.

WednesdayYou find out when somebody asks for the numbers.

What we do about it

A Monday, as we would run it
  1. setupWe generate an address. You forward to it, or the partner sends to it.
  2. 09:00Due passes with nothing matching the sender or subject.
  3. 09:30Grace ends. One alert, naming what we were waiting for.
  4. 11:40It arrives, matched on sender. One closing alert, with the size.

What we need

Nothing installed anywhere. You forward to an address we generate, and tell us what to match on. The full posture.

no credentialmatch on sender or subjectnothing to change for the sender
The monitor, configured

Weekly partner CSV

Where
an address we generate
Match
sender, or a subject line
When
Mondays by 09:00
Grace
30 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 partner emails me the weekly numbers every Monday by 9am, give it 30 minutes.”

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