Connectors
Mailgun
Connect Mailgun for API delivery, provider webhooks, and domain-level sending controls.
Use the Mailgun connector when your team already manages domain authentication, routes, logs, or deliverability operations in Mailgun.
Before you start
- Create a Mailgun API key with sending permissions.
- Verify the sending domain in the correct Mailgun region.
- Confirm whether your Mailgun account is US or EU, then choose the matching connector region.
Setup
flowchart LR
MG[GenieOS] --> Region{Mailgun region}
Region --> US[US API]
Region --> EU[EU API]
US --> Domain[Verified Mailgun domain]
EU --> Domain
Domain --> Recipient[Recipient]
Domain --> Events[Mailgun events]
Events --> MG- Open Settings -> Connectors and choose Mailgun.
- Select the Mailgun region.
- Paste the API key and sending domain.
- Add the GenieOS webhook URL in Mailgun.
- Send a connector test.
Capabilities
| Capability | Support |
|---|---|
| Transactional sends | Yes |
| Broadcast sends | Yes |
| Attachments | Mailgun limits apply |
| Inline images | Mailgun limits apply |
| Webhooks | Accepted, delivered, failed, opened, clicked, complained, unsubscribed |
| Suppressions | Provider events can create GenieOS suppressions |
Webhooks and suppressions
Enable Mailgun webhooks for permanent failures, complaints, and unsubscribes at a minimum. Delivery, open, and click events are useful for complete timelines but may depend on Mailgun tracking settings.
Troubleshooting
- Region errors often look like authentication failures. Confirm the connector uses the same region as the Mailgun domain.
fromerrors usually mean the sender domain does not match the configured Mailgun domain.- Missing opens or clicks usually mean tracking is disabled for the domain.
Mailgun US and EU APIs are separate. Keep the connector region aligned with the domain region to avoid confusing test failures.