[PL] Bob alongside Mailgun

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

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

[PL] What Bob can do today

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

[PL] Where Mailgun still leads

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

[PL] Who this fits

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

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