EmailOctopus Integrations: Native, Zapier, and API
EmailOctopus reaches other software through three doors, and only one is genuinely first-party. The official directory lists roughly 60–70 partners, but the pieces EmailOctopus builds itself number 3: the WordPress plugin, the Zapier app and the REST API v2. Zapier does most of the work — it puts EmailOctopus in front of 8,000+ apps and backs most of the logos in that directory. Everything else is a third-party product built against the public API. There is no marketplace, no OAuth install flow and no transactional surface: no integration can make EmailOctopus send a receipt or a password reset, because the product has no send endpoint.
At a glance
Read the middle number carefully. A Zapier-backed integration is a paid dependency on a third platform with its own task quota and latency, and a card in the directory does not imply a direct connection. If you need real-time list sync at volume, budget for API work against v2. If you want more genuinely native connectors out of the box, MailerLite and Mailchimp both carry deeper first-party catalogues at comparable price points.
Transactional email is out of scope for every integration on this page. EmailOctopus states all emails must be created and sent through the dashboard, and offers no SMTP relay and no send endpoint. Order confirmations, password resets and WordPress system mail need a separate provider — Amazon SES is the one EmailOctopus names, and Sender is a common pick when you want both under one roof.
Integrations directory
Below is the working subset: 25 connectors EmailOctopus documents itself or that buyers actually ask about, grouped by job. Cards are tagged by how the connection is made — NATIVE means the partner calls the EmailOctopus API directly and you configure it inside that product, ZAPIER means the path runs through Zapier and spends tasks. Browse everything in the official directory, and check the integrations and API knowledge base for the setup articles EmailOctopus maintains.
First-party
Native
Zapier
WordPress
Automation & no-code (3)
The official EmailOctopus Zapier app: contacts, tags and triggers wired to 8,000+ tools, and the backbone of most directory listings.
Visual scenario builder moving data between EmailOctopus and hundreds of services, cheaper than Zapier at volume.
Developer-oriented workflow platform with prebuilt EmailOctopus triggers and actions, plus raw code steps.
WordPress & CMS (5)
The official plugin builds sign-up forms by shortcode or block and syncs subscribers — the only first-party CMS connector.
WordPress form plugin with a dedicated EmailOctopus feed add-on and conditional field mapping.
WordPress forms plugin documented by EmailOctopus for direct list subscription, no middleman.
Drag-and-drop WordPress form builder wired through Zapier, so every submission spends a Zapier task.
Syncs WordPress users, WooCommerce customers and membership or LMS rosters into lists on a schedule.
Ecommerce & payments (4)
Sync Shopify customers and order events into lists via Zapier — there is no EmailOctopus app in the Shopify App Store.
Push WooCommerce customers and orders into segments through Zapier, or use FuseWP to stay inside WordPress.
Add or update contacts when Stripe payments, customers or subscription states change, tagged by plan.
Digital-download and membership store that adds buyers to a list on purchase, documented by EmailOctopus.
CRM (3)
Keep HubSpot contacts and EmailOctopus subscribers in step; two-way sync means two Zaps and two task budgets.
Create contacts from Pipedrive people and deal stages, useful for nurturing stalled or lost opportunities.
Move Salesforce leads and contacts into lists; no managed package exists, so field mapping lives in Zapier.
Forms & lead capture (4)
Turn Typeform responses into subscribers with answers mapped to list custom fields and tags.
Popup, slide-in and exit-intent suite with a documented direct connection, consuming no Zapier tasks.
Popup and exit-intent builder that pushes captured emails straight into an EmailOctopus list on submit.
Pipe Meta lead-ad submissions in near real time so the welcome automation fires while intent is warm.
Websites & landing pages (3)
Send Squarespace form and store signups over; embedding the hosted form code block avoids Zapier entirely.
No-code site builder wired to lists through Zapier, or via a custom-code embed of the hosted EmailOctopus form.
One-page site builder with a built-in EmailOctopus form action — pick the provider, supply the list, done.
Newsletter growth & monetisation (3)
Referral and recommendation network for newsletters; official integration launched June 2024.
Referral program software that syncs referred subscribers in and attributes each signup to its referrer.
Marketplace for selling targeted ad placements inside your newsletter to monetise the audience.
Building your own integration
When no card fits, the fallback is the REST API v2 at https://api.emailoctopus.com with an Authorization: Bearer header. Three endpoints cover most integration work: PUT /lists/{list_id}/contacts upserts a contact by email address, PUT /lists/{list_id}/contacts/batch does bulk create-or-update in one call, and POST /automations/{automation_id}/queue triggers an automation from your own code. Collections return at most 100 results per page with cursor pagination. Rate limiting is a token bucket of 100 tokens refilling at 10 per second, about 600 sustained requests per minute; overrun returns HTTP 429 and blocks the connection for up to one minute, so watch the X-RateLimiting-Remaining header. EmailOctopus maintains no official SDKs, and legacy v1.6 keys will not authenticate against v2. See the API v2 documentation and the API limits article.
Frequently asked questions
How do I connect EmailOctopus to WordPress?
Install the official EmailOctopus plugin, paste an API key from account settings, and place a form with the supplied shortcode or block. It captures subscribers only. It does not route WordPress system mail — password resets, comment notifications, order confirmations — because there is no SMTP relay; that needs a transactional provider configured separately. Gravity Forms, Ninja Forms and FuseWP cover deeper needs like conditional feeds and user-role sync.
Does EmailOctopus integrate with Shopify or WooCommerce?
Both, through Zapier rather than a direct app. There is no EmailOctopus listing in the Shopify App Store, so the path is a Zap watching for new customers or paid orders that upserts them into a list. WooCommerce has the same route plus FuseWP, which syncs customers from inside WordPress and avoids per-task costs on a busy store. Neither gives you product blocks or abandoned-cart revenue attribution.
How do I sync Stripe customers to an EmailOctopus list?
Use Zapier. Trigger on New Customer, New Payment or a subscription event, then use the Add or Update Contact action so repeat events update the record instead of erroring on a duplicate. Map the plan name into a custom field or tag so you can segment payers from trials. If task costs get uncomfortable, a Stripe webhook posting to your own endpoint that calls PUT /lists/{list_id}/contacts removes the middleman.
Does EmailOctopus have a native Zapier app, and what does it support?
Yes, and it is one of only three first-party integration surfaces. The app is contact-centric: add or update a contact, find a contact, change a contact’s email address, add or remove a tag, and unsubscribe a contact, with triggers for new and unsubscribed contacts. It cannot send email, create campaigns or edit templates, because the API is read-only on campaigns and has no send endpoint.
How do I add EmailOctopus signup forms to Squarespace, Webflow or Carrd?
Carrd is easiest: it has a built-in EmailOctopus form action, so you pick the provider and supply your list with no code. On Squarespace and Webflow, build the form in EmailOctopus and embed the generated snippet in a code block — it posts directly and costs nothing per submission. The platform’s own form plus Zapier also works but spends a task per signup and delays the welcome automation.
Can I connect EmailOctopus to a CRM like HubSpot or Pipedrive?
Yes, via Zapier for HubSpot, Pipedrive and Salesforce. There is no native CRM connector and no managed package, so mapping and deduplication logic live in the Zap. Plan for direction: pushing CRM contacts into a list is one Zap, feeding engagement data back needs a second Zap and a second task budget. For richer bidirectional behaviour, an ESP with a purpose-built CRM sync costs less effort.
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.
