Communication · Integration
sms77
Add sms77 to your product for your customers, and give your AI agents governed access to it.
sms77 is a European messaging gateway that sends SMS and can turn a message into a spoken call through text to speech, alongside lookups that tell you whether a number is reachable, how it should be formatted and whether it has been ported to another network. An embedded integration sends those messages, reads delivery reports, receives inbound replies and runs the lookups, all under each customer's own key so throughput and credit stay theirs. Sends are deduplicated per event, because a network retry must never turn one alert into two phone calls. The service now trades as seven, so the connector follows that platform while keeping the name this catalogue was published under, which is also why no logo is shown here.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own gateway account so messages go out on their credit rather than a shared pool.
Send an SMS from an event in your product, with retries deduplicated so nobody receives it twice.
Escalate to a text to speech voice call when a message has to be heard rather than read.
Validate a number before sending so a bad record fails inside your product instead of at the carrier.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent sends an approved notification to the recipients you allowed, with every send logged.
An agent reports which messages the carrier failed to deliver and what reason it gave.
An agent looks up a number's format and network before anything is sent to it.
Example prompt
Send the outage notice to the on-call numbers, then tell me which ones the carrier could not reach.
Set up sms77 in 4 steps
- 01Enable the sms77 connector in your fastn dashboard.
- 02Have each customer supply their own gateway API key so sends are billed to them.
- 03Map the message and delivery report fields your product uses, and decide which events trigger a send.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the sms77 integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a sms77 integration without building it. Your customers connect their own sms77 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 sms77 update is not your on-call problem.
- One integration serves your product and your agents. The same governed sms77 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
ClickSend
InfobipOften used alongside
Tools the same teams tend to run next to sms77, across other categories.
Aircall
Calendly
Gong
Google Calendarsms77 integration FAQ
How do I add a sms77 integration to my product?
Enable the sms77 connector in your fastn dashboard, then let each customer authenticate their own sms77 account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no sms77 client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own sms77 account?
Yes. Every connection is scoped to the individual customer, so each authorises their own sms77 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 sms77 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 sends an approved notification to the recipients you allowed, with every send logged.
Who maintains the sms77 integration?
fastn does. When sms77 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 sms77 account?
Yes. Every customer authorises their own sms77 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 sms77 integration?
A common starting point: let each customer connect their own gateway account so messages go out on their credit rather than 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 sms77 integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding sms77 does not change your per-connector cost. You can start free with 3 connected accounts.
Add sms77 to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.