Triggers
Condition Becomes True
When to use it: You want the workflow to fire the moment a record first meets a condition — when it transitions from not matching to matching.
You define the condition using Kanri’s filter builder — the same filters used in reports and groups. The workflow fires once, at the moment the condition becomes true for a record. It won’t fire again for the same record unless the condition goes false and then becomes true again later.
Example uses:
When a member’s subscription status becomes “Expired” → send a re-engagement message.
When an invoice has been overdue for more than 30 days → trigger a late notice sequence.
When a membership’s sessions remaining reaches 0 → alert the member to renew.
How transitions are detected:
Kanri detects condition transitions in two ways:
After supported saved operations — Kanri compares records before and after service-backed
changes to detect a filter changing from false to true. This is not a guarantee that every
possible background update, import, or direct database change is observed.
Daily sweep — for conditions involving date comparisons (like “days since last visit > 30”), Kanri runs a daily sweep to catch transitions caused by time passing rather than a record change.
Date-based transitions are checked daily, not continuously. Scheduled Time Field Due also uses
the daily check; it is not a real-time alternative. Allow for background processing delays and
use a recurring schedule when the automation genuinely needs a selected time of day.

Search terms: