Conditional sends buried in service code
if (plan === "Pro") send("pro_template") else send("basic_template") — repeated across services, impossible to audit.
Stop encoding email routing logic in your application. Define rules that match events to templates — by plan, locale, event type or any payload field. else.events handles the rest.
if (plan === "Pro") send("pro_template") else send("basic_template") — repeated across services, impossible to audit.
Determining which language template to send is custom code in your application or a helper function that grows over time.
If provider A fails, the fallback logic is in your application. Changing providers means code changes across multiple services.
An unexpected email was sent. Figuring out which condition triggered it requires reading code and log traces.
Your application fires a typed event with a user block and a data payload. That is the only application-side responsibility.
Define rules that match on event type, plan, locale, tenant or any payload field. Rules are configured in else.events, not in your code.
Each rule points to a template. Templates are versioned and support multiple locales — managed in the else.events UI.
Configure which provider handles which event types. Switch providers without code changes.
Your application POSTs a typed event to the else.events API. The event includes a type, user block and data payload.
else.events evaluates rules in order. The first matching rule is selected. Rules can match on event type, payload fields, locale or plan.
The matched rule points to a template. else.events selects the correct version and locale variant of that template.
Payload variables are injected into the template. The rendered email is delivered through the configured provider.
The full chain — event, rule matched, template version, delivery status — is recorded in the delivery log.
Event → Rule → Template → Send. Define once, reuse across every product email.