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.
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.
Signup verification and magic link login both contain a one-time URL, but the copy and context differ significantly.
A verification link that silently expires without any indication in the email frustrates users and increases support tickets.
Verification emails built with a raw API call often lack the styling and tone of the rest of the product.
The "resend verification" flow often duplicates the original send logic with subtle differences.
user.email_verification_requested and user.magic_link_requested fire separate events, routing to distinct templates with appropriate copy.
Generate the token and URL in your backend. Include them in the event payload. The template renders the branded CTA.
Include expires_in_minutes. The template renders "This link expires in 30 minutes" without hardcoding.
Your backend generates a new token, fires the same event type. else.events handles the email.
Fire the verification event. else.events delivers the right email through your provider.