Postmark + else.events

Postmark handles sending. else.events handles the workflow.

Postmark is excellent for deliverability. But it does not have event-based routing, multi-locale templates or a no-deploy editing workflow. else.events fills that gap — and can use Postmark as its delivery provider.

What you do not get from Postmark alone

No event-to-email routing layer

Postmark sends emails when you tell it to. You still need to build the logic: which event fires which template, for which locale, for which plan tier.

Template editing requires a developer

Postmark templates live in the dashboard, but your team still needs to know which template to edit, and there is no versioning or approval flow.

No structured event logs

Postmark logs delivery events. But the link between "user fired invoice.payment_failed" and "email delivered at 14:03" lives only in your application code.

Multi-locale and multi-tenant require custom code

Routing to a German template for a German user, or to a tenant-branded template for a white-label customer, requires custom logic in your backend.

else.events + Postmark: a complete SaaS email workflow

Event-based routing on top of Postmark sending

Your app fires events. else.events matches rules, selects the right template and locale, then sends via Postmark. No custom routing code.

Template editing without deployment

Your team edits templates in else.events. Changes go live immediately — no release needed, no developer required for copy changes.

Structured logs linking event to delivery

Every email log entry shows the originating event, the template used and the Postmark delivery status — all in one place.

Multi-locale and multi-tenant out of the box

Rules route to the right locale template automatically. Tenant-specific brand variables apply without custom code.

Postmark alone vs Postmark + else.events

CapabilityPostmark onlyPostmark + else.events
Email delivery & deliverability✓ Excellent✓ Excellent (via Postmark)
Event-to-template routingYour code✓ Rules engine
Template management without deployPartial✓ Full no-deploy editing
Multi-locale templatesYour code✓ Built-in locale routing
Multi-tenant / white-labelYour code✓ Brand variables + workspace routing
Structured event-to-email logsDelivery only✓ Event → rule → delivery chain

else.events adds the workflow layer. Postmark continues to handle sending and deliverability.

Frequently asked questions

Does else.events replace Postmark?
No. else.events is the workflow layer — event routing, template management, locale handling. Postmark is the delivery layer — SMTP infrastructure, deliverability, bounce handling. They complement each other.
What does it cost to use Postmark + else.events together?
You pay Postmark for sending (their pricing by volume) and else.events for the workflow layer (priced by emails sent per month — see the pricing page). The combination is competitive with full-stack tools that bundle everything but charge per contact.
Can I switch from Postmark to another provider later?
Yes. else.events is provider-agnostic. You can switch your delivery provider from Postmark to Resend, Mailgun or SMTP without changing your event logic or templates.
How do I connect Postmark to else.events?
Add your Postmark API key in the else.events workspace settings. Select Postmark as your delivery provider for a workspace or specific rule. Events fire through else.events and are delivered via Postmark.

The workflow layer Postmark does not include

Keep Postmark for deliverability. Add else.events for event routing, template management and structured logs.

  • Works with your existing Postmark account
  • No routing code to maintain
  • Switch providers any time