turboSMTP Integrations: Native, Zapier, and API
turboSMTP is a relay first and a platform second, and its integration surface reflects that. Roughly 25 platforms carry a first-party plugin or a turboSMTP-authored setup guide, one official Zapier app reaches 9,000+ other tools, and anything that accepts a hostname plus a username and password connects with no connector at all. There is no numbered directory on serversmtp.com, so the count below audits documented guides rather than a marketed figure, and it is deliberately smaller than the four-digit numbers marketing-led ESPs quote, because turboSMTP integrates at the protocol layer instead of building bespoke connectors.
Fix one thing before connecting anything: since April 15, 2025 the relay no longer accepts your account login. Every integration here authenticates with a Consumer Key as username and a Consumer Secret as password, generated under API Keys and shown exactly once. Any tutorial older than that date has the wrong credential fields.
At a glance
Read those numbers together and the signal is clear. turboSMTP fits when you already own the application and just need its outbound mail to leave reliably: WordPress, Magento, an ERP, a .NET service. It fits badly when you want a connector that syncs contact records or writes engagement data into a CRM, turboSMTP has none and does not claim to. For that, pair it with a marketing platform or compare Brevo and SMTP2GO.
Integrations directory
The 25 entries below are grouped by what the integration actually is, and the badges decide setup effort. NATIVE means turboSMTP ships a plugin or a step-by-step guide for that product. API means the platform takes plain SMTP credentials or an HTTP POST, with no connector to install. ZAPIER means the official Zapier app. Sources: the third-party services guide and the email client knowledgebase.
WordPress & CMS
E-commerce
Marketing & outreach
Infrastructure
WordPress & CMS (4)
First-party plugin that reroutes wp_mail() through the relay and adds an in-dashboard view of opens, clicks and bounces.
Multi-provider WordPress mailer released May 22, 2025, also driving Gmail and Microsoft 365 OAuth, with failover and logging.
Free WordPress mail-SMTP plugin listed as a supported route if you prefer not to run the first-party plugin.
Enterprise .NET CMS and DXP whose email queue can be repointed at the relay.
E-commerce (3)
First-party guide for pointing Magento 2 transactional mail at the relay: orders, shipping, password resets.
Covered through the WordPress plugin, whose listing calls out WooCommerce transactional email and security alerts.
Official guide for supplying Consumer Key and Secret to PluginHive’s Shopify apps so shipping and label mail relays through turboSMTP.
Automation & frameworks (2)
Official app offering Send Email and Find Email Status across 9,000+ tools, with 0 triggers so far.
Bridge inside the Symfony organisation exposing both transports by DSN, with EU variants and webhook parsing.
Email clients (3)
Documented setup on pro.turbo-smtp.com, though the walkthrough still uses port 25 with security None, override to 465.
Documented client setup; turboSMTP warns against Outlook CC and BCC for mass newsletters and points bulk senders elsewhere.
Covered by the email-client knowledgebase alongside Apple Mail 3.x and iPhone walkthroughs.
Bulk email software (5)
Desktop bulk mailer bundled with turboSMTP as its recommended backend since SendBlaster 4, October 13, 2016.
turboSMTP’s own companion app, launched January 26, 2021, pairing a dedicated relay with per-message tracking.
Self-hosted newsletter manager with no delivery infrastructure, so an external relay is mandatory rather than optional.
Windows bulk-mailing application connectable to the relay through standard SMTP settings.
macOS and Windows bulk mailer with a vendor walkthrough for the host, port and credentials.
Email marketing & outreach (4)
Gmail-based mass-mailing extension pointed at an external relay to escape Gmail’s daily caps.
Prospecting and cold-outreach platform requiring an external SMTP provider for outgoing sequences.
Cold-email sequencing tool that connects to a customer-supplied relay, not its own infrastructure.
Email marketing platform listed in the third-party guide as a bring-your-own-relay consumer.
Business apps & infrastructure (4)
Open-source ERP whose notification, invoice and workflow email needs an external mail server.
Identity platform routing verification, password-reset and MFA email through a custom SMTP provider.
Open-source IoT platform pushing device-alarm and rule-chain notifications through a relay.
RPA mail activities that authenticate against an external SMTP server.
Two caveats. The Zapier app ships 0 triggers, so a Zap can send mail but no turboSMTP event can start one, bounce-driven automation still needs webhooks or polling of /api/v2/analytics. And the official Go SDK is planned, not published, so Go services should use the raw HTTP example or net/smtp.
Frequently asked questions
Does turboSMTP have a WordPress plugin?
Two, both first-party. The original turboSMTP plugin reroutes wp_mail() through the relay and adds an analytics panel for opens, clicks and bounces: version 4.9.8, 400+ installs, tested to WordPress 7.0.4. Pro Mail SMTP, released May 22, 2025, is the multi-provider alternative. Either way the credentials are a Consumer Key and Secret, not your account login.
How do I connect turboSMTP to WooCommerce?
WooCommerce has no mail transport of its own, it hands everything to wp_mail() – so you configure WordPress, not WooCommerce. Install the turboSMTP plugin (or Pro Mail SMTP, or FluentSMTP), set host pro.turbo-smtp.com and port 465 with SSL/TLS, then paste the Consumer Key and Secret. Orders, shipping notices and password resets then all leave through the relay. Place a test order before trusting it.
Is there an official turboSMTP Zapier integration?
Yes, live since September 30, 2025, exposing two actions – Send Email and Find Email Status – across Zapier’s 9,000+ apps. The limitation is 0 triggers: nothing inside turboSMTP can start a Zap. More were promised at launch; none had shipped as of this review.
How do I configure turboSMTP in Magento 2?
turboSMTP publishes a first-party walkthrough. The values match every other integration: host pro.turbo-smtp.com, port 465 for SSL/TLS (fall back to 587 or 2525 only if 465 is blocked), authentication on, Consumer Key as username, Consumer Secret as password. Magento often runs on cloud hosts that block port 25, which is why a stock configuration silently queues mail forever.
Can I use turboSMTP with Laravel or Symfony?
Symfony has a bridge maintained inside the Symfony organisation, symfony/turbo-smtp-mailer, giving both paths by DSN: turbosmtp+smtp://KEY:SECRET@default for the relay and turbosmtp+api://KEY:SECRET@default for the API, plus EU host variants and webhook parsing. Laravel ships no turboSMTP driver, so use the built-in smtp mailer with the standard host, port and credential pair, or the turbosmtp/turbosmtp-client PHP SDK for the API transport.
What is the difference between the turboSMTP plugin and Pro Mail SMTP?
The turboSMTP plugin is single-provider: it routes WordPress mail through turboSMTP and shows the analytics inside wp-admin. Pro Mail SMTP also drives Gmail and Microsoft 365 OAuth, Amazon SES, Brevo, SMTP2GO and generic SMTP, with failover. Take the first if turboSMTP is your only sender; take the second if you want a fallback configured before the day you need it.
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.
