GenieOSdocs
Connectors

Connectors

Send through GenieOS Relay, your transactional ESP, SMTP, or a lifecycle platform while keeping one GenieOS workflow.

Connectors let GenieOS keep the product workflow in one place while the actual delivery can happen through the provider your team already trusts. Templates, approvals, schema contracts, campaigns, suppression checks, audit logs, and delivery events still live in GenieOS.

How connectors work

Every connector follows the same control flow: GenieOS validates the message, checks suppressions, hands the send to the provider, then normalizes provider webhooks back into GenieOS events.

flowchart LR
  App[Your app] --> MG[GenieOS API]
  MG --> Policy[Schema, approval, suppression checks]
  Policy --> Connector[Connector adapter]
  Connector --> Provider[Delivery provider]
  Provider --> Recipient[Recipient]
  Provider --> Webhook[Provider webhook]
  Webhook --> Normalize[GenieOS event normalizer]
  Normalize --> Audit[Send timeline and analytics]

Connector families

FamilyBest forExamples
Managed relayTeams that want GenieOS to own delivery setup and webhooks.GenieOS Relay
Transactional ESPTeams with an existing ESP account, domain reputation, or procurement path.MailerSend, SendGrid, Postmark, Resend, Mailgun, Amazon SES
SMTPLegacy systems or providers that only expose SMTP credentials.SMTP
Lifecycle platformMarketing and lifecycle teams that want downstream journey analytics and suppressions.Iterable

A workspace can keep multiple connectors installed. The active connector is selected per workspace, and GenieOS stores provider credentials server-side rather than exposing them to browsers or SDK clients.

Provider guides

Each guide covers setup, capabilities, webhook behaviour, suppression handling, limits, and troubleshooting:

On this page