[NL] Bob alongside Mailgun

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

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

[NL] What Bob can do today

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

[NL] Where Mailgun still leads

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

[NL] Who this fits

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

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