Connect your own Mailgun account
Send from a domain you have verified in Mailgun. The connection carries both the key and the domain, so it is unambiguous which identity a message leaves as.
What you need from Mailgun
Gather these in the Mailgun portal first. The connection form asks for exactly these fields and nothing more.
| Field | What it is |
|---|---|
| apiKey | API Key. The key for the sending domain. The account-level key also works, but a sending key is the safer one to paste here. |
Credentials are sealed with AES-256-GCM and the console only ever shows a masked value afterwards. Plaintext is never written to logs and never sent back to the browser.
What we configure on the connection
- Sending domain. Required. Mailgun puts it in the API path, so it must match the verified domain exactly.
- Sender address (From). Must be an address on that verified domain.
- Default send pacing: 10 messages per second. This is a conservative starting point, applied per connection, and you can change it at any time. Your real ceiling is set by Mailgun — check your account quota and raise the value to match.
Why teams pick Mailgun
- The sending domain is part of the connection, so the identity is explicit
- Per-domain keys, so the credential can be scoped to one domain
- Domain verification stays in your own Mailgun account
Worth knowing
- A wrong or unverified domain fails at Mailgun rather than here — the error code is recorded on the send so you can see which check rejected it.
What stays on your side
These are yours to hold — and that is the point of bringing your own account: the relationship, the rates and the compliance stay in your name, not ours.
- Account approval and billing terms
- Domain verification, plus the SPF and DKIM records for the domain you send from
- Sender reputation, and any blocklist remediation that follows from it
- The quotas and rate limits Mailgun grants your account
Next
Whaleal Platform currently offers self-service connections to 6 SMS providers, 4 email providers and 3 WhatsApp providers. Underlying the SMS channel is an SMS adapter library of 33 adapters; the ones outside this list are unlocked on request rather than self-service.