Marketing Automation · Integration
Sender
Add Sender to your product for your customers, and give your AI agents governed access to it.
Sender exposes a REST API at api.sender.net/v2 behind a bearer token, and the unit of organisation is a group rather than a list, so adding a subscriber to a group is what puts them into the matching automation. Subscribers are addressed by email address or by subscriber ID, and anything beyond the standard name and email is a per-account custom field that has to be read before you can map data into it. Unsubscribe and bounce state lives on the subscriber record, so a sync that rewrites a contact wholesale can quietly resurrect someone who opted out. Campaign objects are mostly read for reporting, since sending is driven from Sender itself rather than by a single create call. fastn holds each customer's Sender token in its own tenant and keeps the group and field mapping working as accounts change.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Sender account so signups in your product land in the right Sender group automatically
Push product events such as trial start or churn into custom fields so the customer's automations can react to them
Show campaign open and click activity next to each contact inside your own app instead of sending users to Sender
Honour unsubscribes made in Sender by writing the state back to your product's own contact record
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent add or move a subscriber between groups when a support conversation confirms a change of interest, with every write audited per tenant
Have an agent read recent campaign activity and summarise which segments are going quiet
Let an agent correct malformed custom field values on subscribers it flags during a data quality sweep
Example prompt
Which Sender groups had the lowest open rates on last month's campaigns?
Set up Sender in 4 steps
- 01Enable the Sender connector from your fastn dashboard.
- 02Have each customer authorise their own Sender 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 Sender integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Sender integration without building it. Your customers connect their own Sender 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 a Sender update is not your on-call problem.
- One integration serves your product and your agents. The same governed Sender 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 Sender, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMSender integration FAQ
How do I add a Sender integration to my product?
Enable the Sender connector in your fastn dashboard, then let each customer authenticate their own Sender account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Sender client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Sender account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Sender 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 Sender 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 move a subscriber between groups when a support conversation confirms a change of interest, with every write audited per tenant
Who maintains the Sender integration?
fastn does. When Sender 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 a Sender 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 Sender?
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 Sender integration?
A common starting point: let a customer connect their own Sender account so signups in your product land in the right Sender group automatically. 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 Sender integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Sender does not change your per-connector cost. You can start free with 3 connected accounts.
Add Sender to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.