Mailjet Integrations: Native, Zapier, and API

Yes to both. Mailjet for WordPress is authored and maintained by Mailjet itself — the integration page names Mailjet as the developer. It adds subscription widgets, contact sync and campaign management inside wp-admin, and redirects WordPress’s own wp_mail() through Mailjet, so password resets and comment notifications stop leaving via your host’s mail server. WooCommerce support ships in the same line. If you would rather not run another plugin, point any generic SMTP plugin at in-v3.mailjet.com on port 587 instead.

They are not equivalent. WooCommerce is covered by Mailjet’s own extension, bundled with the WordPress plugin family, which syncs customers and order events into contact lists directly. Shopify is not: Mailjet’s page states that new orders, products and customers reach Mailjet by using Zapier. There is no Mailjet app in the Shopify app store, so a Shopify build means a Zapier account, its task quota and its latency — or writing against the API yourself.

HubSpot is the direct one: it syncs Mailjet and HubSpot automatically so you can email CRM contacts and build workflows across both. Salesforce is not. Mailjet’s page says to use "one of our iPaaS partners listed below", naming Zapier and Cloud Elements — there is no Mailjet-maintained managed package on AppExchange. If Salesforce is your system of record and you need field-level bidirectional sync, price that iPaaS layer in first.

The official directory lists 100 integrations across 11 categories, spanning analytics and data, automation, CMS, communication, contact management, CRM, developer tools, e-commerce, finance and operations, forms and surveys, and marketing tools. Only a minority of those 100 are code Mailjet writes: the CMS and e-commerce plugins are genuinely first-party, while many CRM and SaaS entries resolve to a Zapier or other iPaaS connector. Mailjet publishes no Zap count and no API-integration count, so any larger headline number you see elsewhere is inferred, not official.

Both are listed, and both drive the Mailjet REST API rather than a proprietary bridge. n8n matters most for EU-compliance buyers: you can self-host it and keep the orchestration layer in your own infrastructure, which pairs with Mailjet storing data exclusively in EU data centres in Frankfurt and Saint-Ghislain. Make.com is the hosted visual alternative. Both authenticate with your API Key and Secret Key, the same pair the SMTP relay uses.

Three routes, in ascending order of effort and control. First, a listed connector (Zapier, Make.com, n8n) if your CRM is in the directory — fastest to stand up, slowest at volume. Second, the bulk endpoint POST /v3/REST/contact/managemanycontacts, which creates or updates many contacts asynchronously and returns a job reference to poll. Third, event-driven sync: register an Event API callback so opens, clicks, bounces and unsubscribes flow back into the CRM. One structural caveat — each Mailjet API key is a separate contact database, and contacts and lists are not shared between API keys, including the main one. Settle your key topology before you load data; there is no merge operation afterwards.