For monday.com
Automation Run History shows execution. SLA Monitor tracks timing. Neither checks whether an item actually landed where it was supposed to. Declare a guardrail once — Invarly watches in real time and flags the moment reality drifts.
Why this and not what monday already ships
Execution and timing are solved problems. State — whether the process actually finished correctly — isn't, and that's the gap most "the automation is probably fine" incidents live in.
| Layer | Question | Covered by |
|---|---|---|
| Execution | Did the automation run? | monday Automation Run History |
| Timing | How long did it take? | monday SLA Monitor |
| State | Did the process end correctly? | Invarly |
How it works
WHEN a status changes, THEN an item should reach a given state, WITHIN a time limit. Plain terms, no automation recipe.
Real-time webhooks, not polling — Invarly hears about the change the moment monday does.
Reality drifts from the declaration → an open violation appears. Reality catches up → it resolves itself.
Pricing
A flat organization price means everyone who should see a broken workflow can see it — without another approval for a license.
Invarly