Do I need to change my Postmark setup?

No. You add your Postmark server token to else.events. Your existing Postmark account, sending domain and DKIM setup remain unchanged.

Does else.events replace Postmark?

No. else.events sits in front of Postmark. Postmark handles deliverability — else.events handles event routing, templates and rules.

Can I still call Postmark directly for some emails?

Yes. else.events does not prevent direct Postmark API calls. You can migrate incrementally — use else.events for new product emails while keeping existing direct calls.

What if Postmark returns a delivery error?

Delivery errors are surfaced in the else.events dashboard and logs with the full Postmark response, so you can investigate quickly.

Provider integration

Use Postmark with else.events

Postmark handles deliverability. else.events adds event routing, template management, localization and rules on top. Keep the benefits of both.

Connect Postmark Postmark alternative?

Postmark alone leaves gaps in your email workflow

Templates still live in your code

Your app decides which Postmark template to call for which event. That routing logic ends up in your billing service, your auth service, your jobs.

Localization means duplicate templates

A German and an English version of the same email means two Postmark templates to keep synchronized.

No event-to-email audit trail

Postmark logs what it sent. It does not know which product event caused the send or which routing rule matched.

Copy changes still require deployments

Updating a subject line or CTA means changing a template in code and pushing a release.

else.events routes events — Postmark delivers

Add Postmark as your delivery provider

Enter your Postmark server token in else.events. All outgoing emails route through your Postmark account.

Event routing stays in else.events

Your app fires domain events. else.events matches rules, renders the template and calls Postmark on your behalf.

Switch providers without changing your app

Swap Postmark for SMTP or another provider later — your event code stays unchanged.

Combined delivery logs

See the product event, the matched rule, the rendered template and the Postmark delivery status in one place.

// your app fires an event — else.events routes it through Postmark

Your app fires an event. Postmark delivers the email.

await fetch('https://app.else.events/api/events', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${ELSE_EVENTS_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    type: 'invoice.payment_failed',
    user: { email: 'customer@example.com', name: 'Alex' },
    data: { plan: 'Pro', amount: '29.00', currency: 'EUR',
            update_payment_url: 'https://app.example.com/billing' },
  }),
});
// else.events: matches rule → renders template → calls Postmark API

No Postmark API calls in your application code. else.events handles the Postmark delivery — you just fire domain events.

Frequently asked questions

Do I need to change my Postmark setup?: No. You add your Postmark server token to else.events. Your existing Postmark account, sending domain and DKIM setup remain unchanged.
Does else.events replace Postmark?: No. else.events sits in front of Postmark. Postmark handles deliverability — else.events handles event routing, templates and rules.
Can I still call Postmark directly for some emails?: Yes. else.events does not prevent direct Postmark API calls. You can migrate incrementally — use else.events for new product emails while keeping existing direct calls.
What if Postmark returns a delivery error?: Delivery errors are surfaced in the else.events dashboard and logs with the full Postmark response, so you can investigate quickly.

Postmark's deliverability. else.events' workflows.

Connect Postmark as your delivery provider and get event routing, template management and structured logs on top.

Works with your existing Postmark account
No SDK required
Switch providers later without changing your app