Communication · Integration
Sinch
Add Sinch to your product for your customers, and give your AI agents governed access to it.
Sinch is a carrier grade messaging API, so the integration follows how mobile networks actually behave. Messages go out as a batch against a service plan, delivery is asynchronous and reported back per recipient, replies arrive as inbound messages on a number the customer owns, and MMS adds media that has to be hosted somewhere reachable. An embedded Sinch integration sends SMS and MMS, schedules and cancels batches, reads delivery reports, receives inbound messages and maintains recipient groups. The thing to get right is duplication: a retry after a timeout must not send the same text twice, because the recipient sees both. Each customer connects their own account, so sender numbers, throughput and spend stay theirs. fastn keeps those credentials in the tenant they belong to and carries the connector forward.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Sinch account so messages come from their number and their spend, not a shared pool.
Send an SMS or MMS batch triggered by an event in your product, with retries deduplicated per event.
Read delivery reports per recipient so your product acts on a failure instead of assuming a send arrived.
Receive inbound replies and route them into your own workflow, keeping the thread with the right customer.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent drafts a notification and sends it only to recipients you have approved, with every send logged.
An agent reports which messages failed to deliver and what the network gave as the reason.
An agent reads an inbound reply and continues the exchange within scoped permissions.
Example prompt
Did last night's reminder reach everyone, and which numbers did the carrier reject?
Set up Sinch in 4 steps
- 01Enable the Sinch connector in your fastn dashboard.
- 02Have each customer authorise their own Sinch account and confirm which sender numbers they are entitled to use.
- 03Map the message, group and delivery report fields your product uses, then enable inbound handling.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Sinch integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Sinch integration without building it. Your customers connect their own Sinch account inside your product and work their messages, conversations and participants there, with no per-customer code on your side.
- Handle the part that actually costs time: anything sent is user-visible, so duplicates and misfires are immediately embarrassing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Sinch update is not your on-call problem.
- One integration serves your product and your agents. The same governed Sinch connection powers in-product features and gives AI agents scoped, audited access, so you put the right message in front of the right team automatically without wiring it twice.
Used by these teams
Compare with
Twilio
Infobip
MessageMediaOften used alongside
Tools the same teams tend to run next to Sinch, across other categories.
Aircall
Calendly
Gong
Google CalendarSinch integration FAQ
How do I add a Sinch integration to my product?
Enable the Sinch connector in your fastn dashboard, then let each customer authenticate their own Sinch account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Sinch client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Sinch account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Sinch account and only ever sees their own messages, conversations and participants. 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 Sinch 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 drafts a notification and sends it only to recipients you have approved, with every send logged.
Who maintains the Sinch integration?
fastn does. When Sinch 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.
Does each customer connect their own Sinch account?
Yes. Every customer authorises their own Sinch account, so messages, meetings and notifications originate from their workspace under their permissions. You never proxy through a shared account, which also means a customer revoking access affects only their own connection.
How are duplicate notifications avoided?
Sends are deduplicated per event, so a retry after a network failure does not post the same message twice into a channel people are reading.
What can I build with the Sinch integration?
A common starting point: let each customer connect their own Sinch account so messages come from their number and their spend, not a shared pool. 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 Sinch integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Sinch does not change your per-connector cost. You can start free with 3 connected accounts.
Add Sinch to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.