[FR] Bob alongside Mailgun

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

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

[FR] What Bob can do today

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

[FR] Where Mailgun still leads

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

[FR] Who this fits

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

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