Email workflows for SaaS products — Event, Rule, Template, Send

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.

What email logic in your application actually looks like

Conditional sends buried in service code

if (plan === "Pro") send("pro_template") else send("basic_template") — repeated across services, impossible to audit.

Locale selection is application-side logic

Determining which language template to send is custom code in your application or a helper function that grows over time.

Provider routing is hardcoded

If provider A fails, the fallback logic is in your application. Changing providers means code changes across multiple services.

No visibility into which rule fired for which event

An unexpected email was sent. Figuring out which condition triggered it requires reading code and log traces.

Structured workflows — Event → Rule → Template → Send

Events are typed and structured

Your application fires a typed event with a user block and a data payload. That is the only application-side responsibility.

Rules match events to templates

Define rules that match on event type, plan, locale, tenant or any payload field. Rules are configured in else.events, not in your code.

Templates are versioned and locale-aware

Each rule points to a template. Templates are versioned and support multiple locales — managed in the else.events UI.

Provider routing is a workflow configuration

Configure which provider handles which event types. Switch providers without code changes.

How an else.events email workflow works

  1. 01

    Event received

    Your application POSTs a typed event to the else.events API. The event includes a type, user block and data payload.

  2. 02

    Rules evaluated

    else.events evaluates rules in order. The first matching rule is selected. Rules can match on event type, payload fields, locale or plan.

  3. 03

    Template selected

    The matched rule points to a template. else.events selects the correct version and locale variant of that template.

  4. 04

    Email rendered and sent

    Payload variables are injected into the template. The rendered email is delivered through the configured provider.

  5. 05

    Delivery logged

    The full chain — event, rule matched, template version, delivery status — is recorded in the delivery log.

Frequently asked questions

What is an else.events "rule"?
A rule is a condition that matches an incoming event to a template. Rules can match on event type, payload fields (e.g. plan = "Pro"), locale, tenant or a combination. The first matching rule is used.
Can I have multiple rules for the same event type?
Yes. Rules are evaluated in order. You can have a "plan = Pro" rule and a "plan = Free" rule for the same event type, each routing to a different template.
What happens if no rule matches an event?
If no rule matches, no email is sent and the event is logged as unmatched. You can configure alerts for unmatched events on the roadmap.
Can I test a workflow without sending a real email?
You can use a staging workspace with test event payloads to validate rule matching and template rendering before enabling in production.

Email workflows that live in configuration, not in code

Event → Rule → Template → Send. Define once, reuse across every product email.

  • Free during public beta
  • Rules configured in else.events, not in code
  • Full chain logged per delivery