[ES] Bob alongside Mailgun

[ES] Mailgun customers often route multiple domains and regions. Bob sends through [ES] your configured domain [ES] and API key—so receipts, confirmations, and template messages inherit the same DNS reputation work you’ve already done.

[ES] Important: [ES] You’ll provide api_key [ES] and domain [ES] in tenant credentials. Validation endpoints may require specific Mailgun plans; we degrade gracefully when unavailable.

[ES] What Bob can do today

[ES] Send MIME and template-based messages through your Mailgun domain from approved workflows.
[ES] Pull delivery stats for operational visibility within API limits.
[ES] Run email validation when your account supports it—otherwise Bob falls back to safe manual review.

[ES] Where Mailgun still leads

[ES] Domain verification, webhooks, dedicated IPs, and EU/US region choices stay in Mailgun and your infra.
[ES] Marketing blast strategy and compliance are human decisions—Bob executes only what you encode in policy.
[ES] See [ES] Proof Center [ES] for live vs. roadmap tooling.

[ES] Who this fits

[ES] Teams standardized on Mailgun who want the same governed conversational layer as SendGrid users—without switching ESPs.

[ES] Integration marketplace [ES] Join the waitlist [ES] Talk to us