Marketing Automation · Integration
EmailOctopus
Add EmailOctopus to your product for your customers, and give your AI agents governed access to it.
EmailOctopus moved from a v1.6 API that took the key as a request parameter to a v2 API at api.emailoctopus.com that uses a bearer token, and the two differ enough that porting is not a header swap. A contact's identifier in v2 is derived from its email address rather than being an opaque server-generated id, so you can address a contact without having stored anything, but changing an address means creating a new contact. Contacts carry status (subscribed, unsubscribed, pending) plus arbitrary tags and list-specific custom fields, and the custom fields are defined per list, so the same person on two lists can have entirely different field sets. Automations are separate from campaigns and a contact enters one by being pushed into its queue rather than by a campaign send. Double opt-in, when a list has it enabled, means a newly created contact sits in pending and no send will reach it until confirmation, which surprises teams importing existing subscribers. fastn holds each customer's own key, keeps it refreshed, and keeps list writes attributed to the right tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own EmailOctopus account so your product subscribes their users to their own lists
Write list-specific custom fields from your product's profile data when adding a contact
Apply and remove tags on contacts as their status changes inside your product
Read campaign reports and show open, click and bounce counts inside your own dashboard
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent subscribe or unsubscribe a contact on a named list and report the resulting status, with each change audited per tenant
Have an agent push a contact into a specific automation queue when a condition is met
Allow an agent to explain why a contact is still pending on a double opt-in list
Example prompt
How many contacts on our newsletter list are still pending confirmation rather than subscribed?
Set up EmailOctopus in 4 steps
- 01Enable the EmailOctopus connector from your fastn dashboard.
- 02Have each customer authorise their own EmailOctopus account, so calls run under their credentials rather than a shared key.
- 03Decide which campaigns, segments and subscribers your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the EmailOctopus integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an EmailOctopus integration without building it. Your customers connect their own EmailOctopus account inside your product and work their campaigns, segments and subscribers there, with no per-customer code on your side.
- Handle the part that actually costs time: engagement data arrives as a high-volume event stream, so ordering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an EmailOctopus update is not your on-call problem.
- One integration serves your product and your agents. The same governed EmailOctopus connection powers in-product features and gives AI agents scoped, audited access, so you trigger and measure campaigns from inside your product without wiring it twice.
Used by these teams
Compare with
Mailchimp
Marketo
Google AdsOften used alongside
Tools the same teams tend to run next to EmailOctopus, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMEmailOctopus integration FAQ
How do I add an EmailOctopus integration to my product?
Enable the EmailOctopus connector in your fastn dashboard, then let each customer authenticate their own EmailOctopus account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no EmailOctopus client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own EmailOctopus account?
Yes. Every connection is scoped to the individual customer, so each authorises their own EmailOctopus account and only ever sees their own campaigns, segments and subscribers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this EmailOctopus integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent subscribe or unsubscribe a contact on a named list and report the resulting status, with each change audited per tenant
Who maintains the EmailOctopus integration?
fastn does. When EmailOctopus changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I trigger an EmailOctopus campaign from an event in my product?
Yes. Product events can start a campaign, add a contact to a segment, or enrol someone in a journey, so lifecycle messaging follows what a user actually did rather than a nightly export.
Can I read engagement results back from EmailOctopus?
Yes. Results come back scoped per tenant, so your product can act on them without one customer's data mixing with another's. What you get depends on the channel: opens, clicks, bounces and unsubscribes where there are sends, and impressions, spend and conversions where there are campaigns.
What can I build with the EmailOctopus integration?
A common starting point: let a customer connect their own EmailOctopus account so your product subscribes their users to their own lists. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the EmailOctopus integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding EmailOctopus does not change your per-connector cost. You can start free with 3 connected accounts.
Add EmailOctopus to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.