Email verification emails — verification token in the payload, branded template in else.events

Signup verification, magic link login, account activation — each fires a domain event. else.events selects the right template and delivers the verification email through your provider.

Why verification emails often break or look wrong

Verification and magic link emails look identical in code but different in intent

Signup verification and magic link login both contain a one-time URL, but the copy and context differ significantly.

Token expiry is missing from the email

A verification link that silently expires without any indication in the email frustrates users and increases support tickets.

Branding is inconsistent with the rest of the product

Verification emails built with a raw API call often lack the styling and tone of the rest of the product.

Re-sending a verification email is a separate code path

The "resend verification" flow often duplicates the original send logic with subtle differences.

Typed events, distinct templates, one consistent delivery path

Separate event types for each verification scenario

user.email_verification_requested and user.magic_link_requested fire separate events, routing to distinct templates with appropriate copy.

Verification URL in the payload

Generate the token and URL in your backend. Include them in the event payload. The template renders the branded CTA.

Expiry rendered from payload

Include expires_in_minutes. The template renders "This link expires in 30 minutes" without hardcoding.

Resend is just firing the same event again

Your backend generates a new token, fires the same event type. else.events handles the email.

Frequently asked questions

How do I distinguish between email verification and magic link in the template?
Use different event types (user.email_verification_requested vs user.magic_link_requested). Rules route each to its own template with appropriate copy.
What is the difference between email verification and double opt-in?
Email verification confirms ownership of the address for account access. Double opt-in confirms consent for marketing emails. else.events is designed for transactional verification, not marketing opt-in.
Can I customise the verification email per plan or user type?
Yes. Include plan or user_type in the event payload. Rules match on them to select plan-specific template variants.
How do I handle a resend request?
Generate a new token in your backend, invalidate the old one, and fire the same event type again. else.events sends the new verification email.

Verification emails — branded, token-safe, from one event

Fire the verification event. else.events delivers the right email through your provider.

  • Free during public beta
  • Verification URL rendered from payload
  • Separate event types for each scenario