Mailgun’s integration story is developer-first. The catalog runs to roughly 50 first-party plugins across CMS, ecommerce, and backend frameworks, plus another 6,000+ apps reachable through Zapier and Make. The important distinction for buyers is between integrations that expose Mailgun as a drop-in SMTP or API driver (deep, code-owned) and integrations that bridge Mailgun events into other tools (thinner, no-code). The directory below flags each with a type badge so you can tell them apart before committing.
The 28 integrations most relevant to typical Mailgun buyers, grouped by category. Not exhaustive: Mailgun’s ecosystem also covers monitoring hooks (Datadog, PagerDuty), analytics (Segment, Amplitude), and a long tail of community-maintained framework wrappers. Tap any card to open the official install page or SDK repository.
First-class Mailgun mail driver built into Laravel core. Set MAIL_MAILER=mailgun in .env and Mailgun handles delivery, webhooks, and analytics.
Mailgun transport bundle for Symfony Mailer. Handles authentication, region routing (US/EU), and inline attachments via DSN string.
mailgun-ruby gem plugs into ActionMailer. Supports templates, tags, tracking flags, and inbound route parsing via Rack middleware.
Anymail library provides Django email backend for Mailgun with webhook views, delivery status callbacks, and inline attachments.
Official mailgun.js SDK with typed TypeScript definitions. Works with Express, Fastify, NestJS, or any Node backend. Promise-based API.
Flask-Mail extension configured with Mailgun SMTP or REST API keys. Full-stack Python apps with minimal boilerplate.
mailgun-java library with Spring Boot starter support. Sync and async send, template management, and reactive webhook handlers.
Official Mailgun plugin from the WordPress plugin directory. Routes wp_mail() through Mailgun via SMTP or REST API, tracks bounces and complaints.
Popular WordPress mailer plugin with Mailgun integration as one of 15+ supported providers. 5M+ active installs, WPForms-owned.
Community Mailgun module for Drupal 9/10 with Symfony Mailer integration. Configurable log retention and webhook handling.
Ghost publishes newsletters through Mailgun as its bulk email provider. Native integration in the Ghost admin, no code needed.
Routes order notifications, receipts, and shipping updates through Mailgun via the WordPress Mailgun plugin. Transactional-grade delivery for storefronts.
No official Shopify app, but Shopify’s custom email SMTP settings accept Mailgun credentials. Third-party apps like SMTP for Shopify wrap the setup.
Community Mailgun extensions in the Magento Marketplace. Transactional email routing, delivery tracking, and bounce management.
6,000+ apps connected via Mailgun triggers (new email, bounce, delivered, opened) and actions (send email, create list, add member). Universal bridge.
Visual workflow builder (ex-Integromat). More granular than Zapier for multi-step scenarios chaining Mailgun events with other services.
Self-hostable open-source workflow automation with maintained Mailgun community node. GDPR-friendly for teams that cannot use hosted iPaaS.
Serverless workflow platform with Mailgun triggers and actions. Free tier generous for developer prototyping.
Bridge Mailgun delivery events to HubSpot contact timelines via Zapier. No native connector; API-only for custom implementations.
No native AppExchange app. Custom integrations via Marketing Cloud transactional messaging or third-party bridge via Zapier or Workato.
Zendesk can send outbound tickets via Mailgun SMTP. Inbound Mailgun Routes can forward customer emails into Zendesk tickets.
Mailgun is a native Segment source: delivered, bounced, opened, clicked events stream into your customer data platform for downstream routing.
Send Mailgun webhooks to Datadog via HTTP intake. Custom dashboards for delivery rate, bounce rate, and complaint rate SLOs.
Native add-on suite for DMARC monitoring, inbox placement testing, and SPF flattening. Powered by Red Sift partnership under the hood.
Official MCP server shipped Dec 19, 2025. Apache 2.0, Node.js, local execution. Exposes send, templates, lists, stats, suppressions, webhooks, routes, analytics to AI agents.
Bridge access via Zapier’s MCP ecosystem. One MCP tool call uses two tasks from your Zapier quota. Useful for scoped agent action selection.
Official REST API with 7 SDKs (Ruby, PHP, Python, Java, Go, .NET, Node.js). Full coverage of send, events, templates, domains, suppressions, webhooks, routes.
Filter and forward inbound email to your app via HTTP POST or SMTP forward. Expression matching on recipient, from, subject, or headers.
Yes. The official Mailgun plugin lives in the WordPress plugin directory and routes wp_mail() through Mailgun via either SMTP or REST API. It tracks bounces and complaints back into Mailgun’s suppressions and works out of the box with WooCommerce, Contact Form 7, and any plugin using wp_mail().
Mailgun ships approximately 50 first-party plugins and SDKs covering CMS, ecommerce, frameworks, and monitoring tools. Beyond that, Zapier adds another 6,000+ apps through Mailgun triggers and actions, and Make, n8n, and Pipedream provide additional bridges. Anything not covered natively or via workflow tools connects through the REST API v3.
Laravel (built into core), Symfony Mailer (bundled transport), Ruby on Rails (mailgun-ruby + ActionMailer), Node.js / Express / NestJS (mailgun.js SDK), and Spring Boot / Java (mailgun-java) all have first-party or actively maintained community drivers. Django and Flask use the Anymail library for backend integration. Rust, Kotlin, Swift, and Elixir have community wrappers only.
Yes, via the REST API v3. Mailgun provides official SDKs in Ruby, PHP, Python, Java, Go, .NET, and Node.js. The API supports full send, events, templates, mailing lists, suppressions, webhooks, and inbound routes. Rate limits are reputation-based rather than hard per-second caps; the practical constraint is the 0.05% complaint rate ceiling.
Not natively. There is no Mailgun AppExchange app for Salesforce and no HubSpot marketplace connector. Both are typically bridged via Zapier, Workato, or custom API integration. Buyers who need deep CRM sync should consider Postmark (also no native CRM connectors) or SendGrid (Salesforce Marketing Cloud integration exists via parent Twilio).
Yes, via Mailgun Routes. Configure expression-based matching on recipient, from, subject, or arbitrary header fields, then forward matched messages to your app via HTTP POST or SMTP forward. Common use cases: helpdesk email intake, parse-and-store archives, and reply-tracking for outbound campaigns.
Yes. Mailgun shipped an official MCP server at github.com/mailgun/mailgun-mcp-server on December 19, 2025. Apache 2.0, Node.js, local execution only. Covers send_email, templates, mailing lists, delivery stats, suppressions, domain management, webhooks, routes, and analytics queries. See the API + MCP tab for full detail.
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.