Public Beta
Sign in Get API key

Provider integration

Bring your own SMTP provider

Already using Mailgun, SendGrid, Amazon SES or your own SMTP server? Connect it to else.events and add event routing, template management and logs — without changing your provider.

Connect via SMTP See how routing works

SMTP alone is just a pipe

No template management

Raw SMTP gives you sending infrastructure. You still build template rendering, variable injection and localization yourself.

No event-to-email routing

Your application code decides which template to send for which event. That logic multiplies every time you add a plan tier or locale.

No structured delivery logs

SMTP delivery reports tell you if a message was accepted. They do not tell you which product event triggered the send.

Provider lock-in by accident

Switching providers means updating SMTP credentials across every service that sends email.

else.events adds a workflow layer over your SMTP provider

Add SMTP credentials once

Enter your SMTP host, port and credentials in else.events. All outgoing emails route through your SMTP provider.

Event routing on top of your existing infrastructure

Your app fires events. else.events matches rules, renders templates and sends via your SMTP connection.

Switch providers in one place

Change SMTP credentials in else.events — no application code changes needed.

Delivery logs with context

Every sent email is logged alongside the triggering event and matched rule.

// event → else.events → your SMTP provider

Same event API — any SMTP provider delivers.

curl -X POST https://app.else.events/api/events \
  -H "Authorization: Bearer $ELSE_EVENTS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "user.password_reset_requested",
    "user": { "email": "user@example.com", "name": "Jamie" },
    "data": {
      "reset_url": "https://app.example.com/reset/abc123",
      "expires_in": "30 minutes"
    }
  }'

The same event call works regardless of which SMTP provider you configure. Switch providers without touching your application.

Related topics

Frequently asked questions

Which SMTP providers are supported?
Any standard SMTP provider — Amazon SES, Mailgun, SendGrid SMTP relay, Mailersend, your own server. If it speaks SMTP, it works.
Is SMTP or Postmark better for deliverability?
Deliverability depends on your sending domain, DKIM/SPF setup and sending volume — not the integration type. else.events does not change provider-level deliverability.
Can I switch from SMTP to Postmark later?
Yes. Update the provider configuration in else.events. Your event-sending code does not change.
Do I need to configure SMTP credentials per workspace?
Yes. Each workspace has its own provider configuration, so multi-tenant setups can route through different providers per tenant.

Your SMTP provider. else.events workflows.

Connect any SMTP provider and get event routing, template management and logs without changing your infrastructure.

  • Works with any SMTP provider
  • No SDK or code changes needed
  • Switch providers later in one place
Connect via SMTP See how routing works