
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.
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.
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.
Deepest connector: customers, catalogue and full commerce event stream; since June 2026 Shopify can also host DNS for sender and link domains.
Official wp-omnisend plugin, last committed June 2, 2026, syncing customers, orders and cart events.
One-click integration covering store, catalogue and order syncing with no code required.
Native app connection for Wix stores covering contact capture and commerce events.
Lets Ecwid merchants run Omnisend email and SMS directly from the store admin.
Native, but officially requires a Big Cartel Platinum plan, lower tiers block third-party integrations outright.
Omnisend-maintained bridge connecting SureCart checkout data to contacts and events.
Core wp-omnisend plugin adds signup forms and contact sync to any WordPress site, with its own guide in the docs.
Omnisend-maintained plugin pushing Gravity Forms submissions in as contacts with mapped fields.
Omnisend-maintained bridge syncing Contact Form 7 entries to Omnisend contacts.
Official plugin syncing membership level and status, so automations can key on renewal or lapse.
Official plugin connecting LifterLMS course enrolment events to Omnisend workflows.
Added June 15, 2026: subscription and billing events become automation triggers.
Syncs points, tiers and reward events so Omnisend can trigger balance and tier-upgrade messages.
Passes LoyaltyLion loyalty state into Omnisend segments and automation triggers.
Added August 1, 2026: affiliate program events trigger email and SMS workflows.
Surfaces subscriber and campaign context inside Gorgias tickets, so agents see lifecycle state mid-ticket.
Added to the App Market in June 2026, linking ticket activity to Omnisend contact profiles.
Pulls Lead Ads submissions into Omnisend lists automatically, with no spreadsheet step.
Syncs Omnisend segments to Google Ads customer match, so retargeting reuses email segmentation.
Added June 6, 2026: Unbounce landing page leads feed directly into Omnisend automations.
Official app reaching 9,000+ apps, with New Contact and Updated Contacts triggers plus campaign, subscriber, event and template actions.
Make publishes an Omnisend module set on the public REST API; maintained by Make, not Omnisend.
Official hosted MCP server at mcp.omnisend.com/v2/mcp, OAuth-authenticated, exposing the API to Claude, ChatGPT and Cursor via 7 meta-tools.
Self-serve since May 14, 2026: imports Klaviyo segments from Apps › Klaviyo Data Import Tool.
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.
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.
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.
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.
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.
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.
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.
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.