Marketing Automation · Integration
Elastic Email
Add Elastic Email to your product for your customers, and give your AI agents governed access to it.
Elastic Email spans both marketing sending and transactional sending, but the v4 API genuinely exposes campaigns, lists and rule-based segments alongside contacts, which is why it belongs here rather than under transactional email. Version 4 at api.elasticemail.com/v4 authenticates with an X-ElasticEmail-ApiKey header, not a bearer token, and the older v2 surface is still live but takes the key as a query parameter and returns HTTP 200 with a success flag of false on failure, so error handling written against v2 will silently swallow problems. Contacts are keyed by email address rather than an opaque id, meaning an address change is a delete and recreate. Segments are defined by a query expression over contact fields rather than a stored membership list, so segment size is evaluated at read time. Sending is blocked until a domain is verified with SPF and DKIM records, and suppression entries live in their own collection separate from contact status. fastn stores each customer's own API key, keeps it rotated, and keeps campaign and contact writes attributed per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Elastic Email account so your product writes contacts into their lists rather than a shared one
Push segment definitions from your own product filters and read back the evaluated contact counts
Create and schedule a campaign from a template your product renders, then read delivery statistics
Check a customer's domain verification status during onboarding and tell them which DNS record is missing
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent add or update contacts on a named list and report what changed, with every write audited per tenant against that tenant's own API key
Have an agent read campaign statistics and summarise open and bounce rates for a period
Allow an agent to check the suppression list before a customer asks why a specific address stopped receiving mail
Example prompt
How did our last Elastic Email campaign perform, and how many addresses bounced or unsubscribed?
Set up Elastic Email in 4 steps
- 01Enable the Elastic Email connector from your fastn dashboard.
- 02Have each customer authorise their own Elastic Email 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 Elastic Email integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Elastic Email integration without building it. Your customers connect their own Elastic Email 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 Elastic Email update is not your on-call problem.
- One integration serves your product and your agents. The same governed Elastic Email 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 Elastic Email, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMElastic Email integration FAQ
How do I add an Elastic Email integration to my product?
Enable the Elastic Email connector in your fastn dashboard, then let each customer authenticate their own Elastic Email account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Elastic Email client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Elastic Email account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Elastic Email 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 Elastic Email 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 add or update contacts on a named list and report what changed, with every write audited per tenant against that tenant's own API key
Who maintains the Elastic Email integration?
fastn does. When Elastic Email 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 Elastic Email 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 Elastic Email?
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 Elastic Email integration?
A common starting point: let a customer connect their own Elastic Email account so your product writes contacts into their lists rather than a shared one. 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 Elastic Email integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Elastic Email does not change your per-connector cost. You can start free with 3 connected accounts.
Add Elastic Email to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.