Ecommerce email platform Soundest until October 2017; Lithuanian, founder-run, never acquired
Omnisend logo

Omnisend Integrations: 280 Native + Zapier + API

Last verified Aug 27, 2026

Omnisend claims 200+ apps in its integrations headline and 250+ pre-built integrations in the body copy of the same page. The verifiable numbers are smaller and more useful: roughly 11 one-click storefront connectors, a set of Omnisend-maintained WordPress bridge plugins, 9,000+ apps through the official Zapier app, and 130+ REST endpoints across 14 API groups for everything the catalogue misses. Every route is contact-and-event based. Omnisend ships no SMTP relay, so data enters as contacts, products and commerce events, never as an addressed message.

That shapes how to read the directory below: a native integration pushes structured commerce state in automatically, while API and Zapier entries are the escape hatches for everything else. If what you need is an SMTP endpoint for WordPress password resets or WooCommerce system mail, that is a different vendor. Omnisend’s own guidance points readers at Postmark, MailerSend, Amazon SES and Brevo.

At a glance

250+
Pre-built integrations
Headline says 200+, body copy says 250+. About 11 are one-click storefronts.
9,000+
Apps via Zapier
Official Zapier app. Triggers poll, so 15-minute latency on Zapier’s free plan.
130+
REST API endpoints
Across 14 groups on API version 2026-03-15, plus two hosted MCP servers.

In short: the catalogue covers the ecommerce stack, Zapier covers the long tail at the cost of latency, and the API covers the rest at 400 requests per minute, except the analytics endpoints, capped at 55 calls per 24 hours.

Integrations directory

The 25 integrations below are verifiable against Omnisend’s support articles, GitHub organisation, API docs and 2026 changelog. Omnisend publishes no machine-readable catalogue and its own totals contradict each other, so check the live integrations page and the supported integrations article before committing.





Ecommerce platforms (7)

WordPress and lead capture (3)

Subscriptions, membership and LMS (3)

Loyalty, reviews and affiliate (3)

Support and helpdesk (2)

Ads and landing pages (3)

Automation, AI and migration (4)

Two notes before you scope an implementation. Zapier, Pabbly and Appy Pie all publish “Omnisend + SMTP” integration pages; those wire Omnisend to a separate SMTP service you already own and contain no Omnisend hostname. If your storefront is missing above, the supported route is the REST API plus the JavaScript snippet, the same custom-integration path Klaviyo and ActiveCampaign expect.

Frequently asked questions

Which ecommerce platforms does Omnisend integrate with natively?

Shopify and Shopify Plus, WooCommerce, BigCommerce, Wix, Ecwid by Lightspeed, PrestaShop, nopCommerce, Big Cartel, Shoplazza and SureCart, roughly 11 one-click storefronts. Shopify is deepest and gets new capability first: it became a supported DNS provider for sender and link domains in June 2026. Big Cartel requires a Platinum plan, because lower tiers block third-party integrations.

How do I connect Omnisend to WooCommerce or WordPress?

Install the official wp-omnisend plugin (listed as Omnisend for WooCommerce) and connect your account. It is the closest thing to a first-party SDK Omnisend ships, last committed June 2, 2026, and it syncs customers, orders and cart events while adding signup forms. What it does not do is carry system mail: password resets and WooCommerce order emails still need a provider such as Postmark behind an SMTP plugin.

Does Omnisend work with Zapier, and how many apps can it reach?

Yes, through the official Omnisend Zapier app, reaching the 9,000+ apps on the Zapier network. Triggers are New Contact and Updated Contacts, both polling rather than webhook-driven, which means a 15-minute interval on Zapier’s free plan. Actions cover Create Subscriber, campaign create, send, cancel, update and copy, Send Customer Event, and template operations. For latency-sensitive work, POST to the Events endpoint directly instead of polling.

How do I integrate Omnisend with a custom or unsupported store platform?

Use the REST API at https://api.omnisend.com/api with the Omnisend-Version: 2026-03-15 header, plus the JavaScript tracking snippet on the storefront. Push contacts to Contacts, catalogue to Products and Categories, and commerce state to Events using documented names such as “started checkout” and “placed order”. Two traps: monetary values are floats in store currency, not integer cents, and carts and orders are no longer readable resources, so your store must stay the system of record.

How do I migrate from Klaviyo or Mailchimp to Omnisend?

For Klaviyo there is a first-party path: the Klaviyo Data Import Tool became self-serve on May 14, 2026 and imports segments from Apps › Klaviyo Data Import Tool. For Mailchimp and other sources, export contacts and import through the UI or the Batch API, capped at 100 actions per batch. Either way, pause automation workflows before backfilling historic events: Omnisend’s batch documentation warns that imported events fire live automations regardless of timestamp.

Can I connect multiple stores or brands to one Omnisend account?

Rate limits and the API model are scoped per brand, and connecting a brand through the Brands endpoint is only possible via OAuth 2.0, not with an API key. Multi-store setups are therefore separate brands, each with its own credentials and its own 400 requests-per-minute budget. OAuth credentials are not self-serve: you request them through an official form and Omnisend replies in 1-3 business days, so build that into any multi-brand rollout.

AAlaa Touil RRabeb How we test →

This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.