What you can do
Three ready-to-use temporal triggers plus seven events already emitted by the CRM, invoicing and AML modules.
Temporal triggers
invoice.unpaid_after_days, aml.expiring_in_days, deal.stale_in_stage_days. Evaluated by a targeted SQL query at each tick (every 2 minutes), capped at 500 candidates.
Business events
invoice.paid, invoice.partially_paid, deal.won, deal.lost, deal.stage_changed, aml.completed, aml.risk_high. Emitted automatically after every committed transaction.
AND conditions with 11 operators
eq, neq, gt, gte, lt, lte, in, nin, contains, exists, not_exists. Evaluated against the trigger payload; OR = two automations to keep the DSL trivial.
Bucket-based deduplication
The same invoice can hit 7/15/30-day cascades without conflict because the dedupeKey encodes the bucket. A state change (deal stage, etc.) auto-resets the counter.
How it works
Three steps to wire a rule that matches exactly what you need.
- 1
Pick the trigger
In the builder, select Temporal or Event. For temporal, choose the rule and fill in the parameters (e.g. { days: 15 }).
- 2
Add conditions (optional)
One to many conditions filter the candidates. Field uses dot notation (invoice.balanceCents), operator from the list, value typed per operator.
- 3
Check the available payload
Each trigger exposes a documented payload (invoice, deal, assessment, …) that feeds the conditions and the {{path}} interpolation in actions.