[JA] Bob alongside Mailgun

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

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

[JA] What Bob can do today

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

[JA] Where Mailgun still leads

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

[JA] Who this fits

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

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