Three trigger families: events (something happened — reply, signal, stage change), conditions (something became true — score crossed 80), and schedules (time-based — every Monday 8am). Events are instant; condition triggers evaluate continuously.
Event triggers
Fire on discrete happenings: record created/updated, reply received, meeting booked, signal fired, sequence exited, webhook received. Latency: seconds.
Condition triggers
Fire when a state becomes true: ICP score crosses a threshold, account goes 30 days without touch, fill-rate drops below target. Evaluated continuously against record changes — fires once per record per condition-entry (with optional re-fire rules).
Schedule triggers
Cron-style: daily digests, weekly hygiene sweeps, monthly re-enrichment. Timezone-aware, with a run window and overlap protection (a slow run won't stack on the next).
Combining
Triggers OR-combine on one workflow (run on event X or schedule Y); use conditions inside the workflow for AND logic. Complex trigger logic is usually a sign you want two workflows.
