Bob alongside Mailgun

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

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

What Bob can do today

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

Where Mailgun still leads

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

Who this fits

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

Integration marketplace Join the waitlist Talk to us