A single product event — 'invoice paid', 'shipment delayed', 'risk score crossed threshold' — usually triggers more than one message. Event-driven flows let you express that in a visual editor (or YAML, if you prefer) instead of scattering send calls across your codebase.
Each capability ships on the standard plan. Nothing in this list is an upsell or a separate product line.
Drag-and-drop flow building stays in sync with a YAML representation you can review in Git. Marketing and product can iterate on copy while engineering keeps the source of truth where the rest of the platform lives.
Branch on properties from the triggering event ('amount > $500'), on user attributes you've pushed to 4notify ('account_tier = enterprise'), or on the state of prior steps ('email step bounced'). No code, no SQL.
Try email first; if the recipient hasn't opened it in 4 hours and the event is still relevant, fall back to SMS. Cascade logic understands the cost difference between channels so you don't fire SMS at every recipient by default.
Multi-tenant SaaS rarely wants the exact same copy for every customer. Per-tenant overrides apply on top of the canonical flow — change the brand name, the sender domain, or the WhatsApp template without duplicating logic.
Every step in a flow is observable: enter/exit counts, branch hit-rates, average dwell time, and per-step cost. You can answer 'how much did this journey cost us last month' in a single dashboard rather than a spreadsheet of channel exports.
Scheduled multi-message campaigns with time-zone awareness and behavioral exits.
Build segments from product events and user attributes; targets stay live as data changes.
Run A/B and multivariate tests on subject lines, send times, and content blocks with confidence intervals.
Reach customers on the channel they actually open — email, US-native SMS, WhatsApp Business, and any system you can point a webhook at.
Know what happened to every message — and why — without piecing it together from carrier exports and inbox screenshots.
