Transactional Email · Integration
Amazon SES
Add Amazon SES to your product for your customers, and give your AI agents governed access to it.
Embed an Amazon SES integration so your customers can send transactional and lifecycle email from their own SES account inside your product, and so your agents can read delivery outcomes under per-tenant governance. Sends are deduplicated per event so a retry does not mail the same person twice, and bounces and complaints come back as events your product can act on. fastn handles each customer's credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers send email from their own verified SES identities and domains, so mail comes from their brand.
Create and update email templates in your product and send templated messages against them.
Read and manage the account suppression list so bounced and complained addresses stay suppressed.
Trigger your product on delivery, bounce, and complaint events, and read sending statistics for reporting.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks whether a message was delivered, bounced, or suppressed before replying to a customer.
An agent sends a templated message within governed permissions and logs what was sent.
An agent reacts to a complaint event and adds the address to the suppression list.
Example prompt
Show bounce and complaint rates for the last seven days and list the domains driving them.
Set up Amazon SES in 4 steps
- 01Open the Amazon SES connector from your fastn dashboard.
- 02Have each customer authenticate their AWS account with least-privilege SES permissions.
- 03Map the sending identities and templates your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Amazon SES integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Amazon SES integration without building it. Your customers connect their own Amazon SES account inside your product and work their messages, templates and delivery events there, with no per-customer code on your side.
- Handle the part that actually costs time: deliverability is the whole game, and it is decided by bounces, complaints and the reputation of the sending domain rather than by anything in the send call. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Amazon SES update is not your on-call problem.
- One integration serves your product and your agents. The same governed Amazon SES connection powers in-product features and gives AI agents scoped, audited access, so you send the mail your product owes its users and know what happened to it without wiring it twice.
Used by these teams
Works well with
Amazon SNS
HubSpot
SlackOften used alongside
Tools the same teams tend to run next to Amazon SES, across other categories.
Notion
Box
Shopify
StripeAmazon SES integration FAQ
How do I add an Amazon SES integration to my product?
Enable the Amazon SES connector in your fastn dashboard, then let each customer authenticate their own Amazon SES account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Amazon SES client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Amazon SES account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Amazon SES account and only ever sees their own messages, templates and delivery events. 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 Amazon SES integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent checks whether a message was delivered, bounced, or suppressed before replying to a customer.
Who maintains the Amazon SES integration?
fastn does. When Amazon SES 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 each customer send from their own domain with Amazon SES?
Yes, and it is the reason to do this per tenant rather than through one shared key. Sending reputation attaches to the domain, so a customer sending from their own verified domain in Amazon SES carries their own deliverability rather than inheriting yours or damaging it.
How do bounces and complaints come back from Amazon SES?
As records rather than log lines. Hard bounces, spam complaints and unsubscribes become suppression state you can read per tenant, so your product can stop mailing an address that already failed instead of sending into a hole and quietly burning the customer's sending reputation.
What can I build with the Amazon SES integration?
A common starting point: send email from their own verified SES identities and domains, so mail comes from their brand. 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 Amazon SES integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Amazon SES does not change your per-connector cost. You can start free with 3 connected accounts.
Add Amazon SES to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.