Moosend Integrations: 42 Native + Zapier + API

Moosend publishes 82 integrations across its official directory, of which 43 are native connectors and the remainder are Zapier tiles. The Zapier app is the widest surface: it reaches Zapier’s 9,000+ apps, and since Moosend is not a Zapier premium app those Zaps run on the free plan. Anything a prebuilt connector misses goes through the REST API v3 at https://api.moosend.com/v3, or through the account relay documented on the SMTP settings tab. The honest shape of the catalogue: strong on ecommerce carts, forms and list hygiene, thin on CRM and support.

At a glance

Integrations directory

The official directory at moosend.com/integrations lists 82 entries under three filters: All, Native and Via Zapier. The 43 native figure comes from the Native view; the remaining 39 or so tiles are Zapier bridges. Below are the 26 connectors most implementations need, tagged by how the connection is really made. ZAPIER means a third-party relay with its own task quota, not a first-party sync.

Ecommerce (5)

CMS and landing pages (2)

CRM and customer data (5)

Forms and lead capture (5)

Automation and no-code (3)

Email verification and list hygiene (2)

Support and messaging (2)

Developer and deliverability (2)

Choosing between native, Zapier and the API

The three routes are not interchangeable. A NATIVE ecommerce connector also loads the Moosend tracking script, so product-view, cart and purchase events reach automations, a Zapier bridge cannot reproduce that, because it carries records, not browsing events. A ZAPIER tile adds a second vendor to the failure path plus its own task quota and polling interval: right for low-volume CRM and support syncs, wrong for a high-frequency subscriber feed. Only the API route gives you control over batching, which matters because bulk import via POST subscribe_many is capped at 2 calls per 10 seconds against 10 calls per 10 seconds for single subscribe. One structural caveat before you design around callbacks: Moosend’s webhooks exist only as a “post a webhook” action inside an automation, with no endpoint to register subscriptions, no published catalogue of delivery events such as bounce or complaint, and no documented signature scheme. Buyers who need first-class event webhooks should weigh Brevo or GetResponse on that axis specifically.

Transactional mail and the SMTP surface

Moosend lists its relay as a directory entry rather than burying it as a setting. It is enabled per account under More › Settings › Direct SMTP and authenticates with your Moosend account login credentials, there is no separate SMTP-only credential to provision, unlike a transactional-first provider such as MailerLite. Sub-accounts carry the Moosend domain prefix in the username, in the form myaccount\username, and need a sub-account password created first. Two facts govern any integration that sends through Moosend rather than merely syncing contacts: the encrypted submission path is smtp.mailendo.com on port 587 with STARTTLS, ports 465 and 25000 having been retired on October 1, 2025; and POST /campaigns/transactional/send is capped at 6 calls per second, the number to size queue concurrency against. Full DNS records and setup steps live on the SMTP settings tab.

Frequently asked questions