Marketing Automation · Integration
Emelia
Add Emelia to your product for your customers, and give your AI agents governed access to it.
Emelia is a cold outreach sequencer, so its campaigns are multi-step drip sequences tied to connected sending mailboxes rather than one-off broadcasts. The API at api.emelia.io takes a key in a header rather than a bearer token, and a campaign only sends once at least one email account is connected and warmed, which means a campaign created purely through the API can sit idle with no obvious error. Contacts are added to a campaign directly or via a contact list, and the same address already present in another running campaign is skipped rather than duplicated, which is deliberate but makes import counts look wrong. Activity is event-shaped: sent, opened, clicked, replied, bounced and unsubscribed all arrive as separate records, and a reply stops the sequence for that contact automatically. Daily sending limits are per connected mailbox, not per campaign, so throughput is a property of the account rather than the request. fastn holds each customer's own key, keeps it current, 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 Emelia account so sequences your product creates run from their mailboxes and their limits
Push qualified leads from your product straight into a named campaign as contacts
Read activity events and mark a lead as engaged in your own model when a reply arrives
Show which connected mailboxes are near their daily sending limit before a customer launches a campaign
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent add a contact to a campaign and report whether it was skipped as a duplicate, with every write audited per tenant against that tenant's own key
Have an agent summarise reply and bounce rates across running campaigns
Allow an agent to pause a campaign when the bounce rate crosses a threshold a customer set
Example prompt
Which Emelia campaigns are getting replies, and which ones are just bouncing?
Set up Emelia in 4 steps
- 01Enable the Emelia connector from your fastn dashboard.
- 02Have each customer authorise their own Emelia 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 Emelia integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Emelia integration without building it. Your customers connect their own Emelia 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 Emelia update is not your on-call problem.
- One integration serves your product and your agents. The same governed Emelia 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 Emelia, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMEmelia integration FAQ
How do I add an Emelia integration to my product?
Enable the Emelia connector in your fastn dashboard, then let each customer authenticate their own Emelia account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Emelia client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Emelia account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Emelia 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 Emelia 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 a contact to a campaign and report whether it was skipped as a duplicate, with every write audited per tenant against that tenant's own key
Who maintains the Emelia integration?
fastn does. When Emelia 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 Emelia 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 Emelia?
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 Emelia integration?
A common starting point: let a customer connect their own Emelia account so sequences your product creates run from their mailboxes and their limits. 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 Emelia integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Emelia does not change your per-connector cost. You can start free with 3 connected accounts.
Add Emelia to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.