Notification email looks nothing like the product
Inconsistent branding in notification emails makes users second-guess authenticity.
SaaS email template
Fire notification.created with the notification type and relevant context. else.events routes to the right notification template and delivers instantly.
Inconsistent branding in notification emails makes users second-guess authenticity.
"You have a new comment" with no link to the comment is useless. Users open the app and spend 30 seconds finding what they were notified about.
Firing notification emails regardless of user preference creates unsubscribe churn.
Notification emails in one language only miss users who set a different locale.
Include the link to the comment, task or project in the event payload. The template renders a "View comment" CTA button that goes directly there.
Rules match on notification_type to route to different notification templates — comment, mention, status change, alert.
Your backend checks user notification preferences before firing the event. else.events handles the email for every event it receives.
Include the recipient's locale. The right language notification template is selected automatically.
{{ user.name }}Recipient name{{ data.notification_type }}Type of notification — comment, mention, status_change, alert{{ data.actor_name }}Name of the person who triggered the notification{{ data.subject }}Notification subject (e.g. "new comment on Project X"){{ data.action_url }}Deep link to the relevant object in the app{{ data.preview }}Short preview text of the notification contentDeep link to the relevant object, notification type from the payload, locale routing.