[IT] Bob alongside Mailgun

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

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

[IT] What Bob can do today

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

[IT] Where Mailgun still leads

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

[IT] Who this fits

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

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