Transactional Email integrations

Your customers connect their own account, and your product reads and writes their messages, templates, delivery events through one governed connection. Send the mail your product owes its users and know what happened to it.

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 across every connector in this category, so that work does not land in your backlog.

Yes. Every connection is scoped to the individual customer, so each authorises their own account and only ever reaches their own messages, templates, 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.

Start with whichever your customers already run, not with the largest vendor. All 5 connectors here share one interface in your product, so adding a second is configuration rather than another integration project, and the order you add them in does not lock anything in.

Yes. Every connector here is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited, so an agent reaches exactly what that customer authorised and nothing else.