Marketing Automation · Integration
Acumbamail
Add Acumbamail to your product for your customers, and give your AI agents governed access to it.
Acumbamail's API is a flat method style interface at acumbamail.com/api/1/{method}/, called with form encoded parameters rather than a JSON body. Two parameters matter on every call: auth_token, taken from the API section of the account, and response_type set to json, because the default response format is XML and clients that assume JSON will simply fail to parse. Methods are named as verbs such as getLists, addSubscriber and getCampaignTotalInformation, so there are no REST resource paths or HTTP verbs to map onto. Subscribers are keyed by email within a list, and adding an address that already exists updates it rather than creating a duplicate, which makes idempotent syncing straightforward. The same account also covers SMS and transactional sending, so one token reaches further than a customer may expect and scoping matters. fastn stores each customer's auth token, keeps the JSON parameter and method names right, and handles upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Acumbamail account so their lists and subscribers stay in step with your product
Add or update subscribers on a list as records change in your app, relying on email keyed upsert to avoid duplicates
Pull campaign totals such as opens, clicks and bounces into your own reporting views
Remove or unsubscribe contacts automatically when they opt out in your product, so consent stays consistent
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent how a named campaign performed and have it compare against the previous send
Have an agent add a subscriber to a list with the correct merge fields, audited per tenant against their token
Let an agent report which lists a given email address currently appears on before a send goes out
Example prompt
How many people opened the June newsletter, and how does that compare with May?
Set up Acumbamail in 4 steps
- 01Enable the Acumbamail connector from your fastn dashboard.
- 02Have each customer authorise their own Acumbamail 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 Acumbamail integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Acumbamail integration without building it. Your customers connect their own Acumbamail 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 Acumbamail update is not your on-call problem.
- One integration serves your product and your agents. The same governed Acumbamail 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 Acumbamail, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMAcumbamail integration FAQ
How do I add an Acumbamail integration to my product?
Enable the Acumbamail connector in your fastn dashboard, then let each customer authenticate their own Acumbamail account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Acumbamail client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Acumbamail account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Acumbamail 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 Acumbamail integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent how a named campaign performed and have it compare against the previous send
Who maintains the Acumbamail integration?
fastn does. When Acumbamail 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 Acumbamail 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 Acumbamail?
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 Acumbamail integration?
A common starting point: let a customer connect their own Acumbamail account so their lists and subscribers stay in step with your product. 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 Acumbamail integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Acumbamail does not change your per-connector cost. You can start free with 3 connected accounts.
Add Acumbamail to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.