Communication · Integration
MSG91
Add MSG91 to your product for your customers, and give your AI agents governed access to it.
MSG91 is an Indian communications provider whose API is served from control.msg91.com/api/v5 and authenticates with an authkey header rather than a bearer token; a wrong or missing key returns an authentication failure body with a 200 status, so status-code-only error handling will miss it. Sending is template-driven: the flow endpoint takes a template_id created in the panel plus variables, and free-form SMS to Indian numbers is blocked by TRAI DLT rules, so the template and the sender ID must be registered against a DLT entity before anything delivers. The OTP endpoints manage generation, verification and retry over SMS or voice on MSG91's side, so you do not store the code yourself. Delivery reports arrive by webhook or are polled from the reports endpoints, and the per-recipient status codes are numeric rather than named. Numbers are expected with the country code and no plus prefix in several endpoints, which is a frequent cause of silent failures. fastn holds each customer's authkey and template scope separately and keeps the connection maintained.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own MSG91 account so messages are sent under their sender ID and DLT registration
Send OTP verification over SMS or voice from your product without storing codes yourself
Trigger templated SMS and WhatsApp notifications tied to events in your app
Show per-recipient delivery reports next to the record that triggered the message
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent send only from templates a tenant has pre-approved, since unregistered templates will not deliver
Have an agent investigate failed deliveries and report the status codes, audited per tenant
Require human approval before an agent triggers a bulk send to a large recipient list
Example prompt
Show me the delivery report for the OTP messages we sent through MSG91 this morning.
Set up MSG91 in 4 steps
- 01Enable the MSG91 connector from your fastn dashboard.
- 02Have each customer authorise their own MSG91 account, so calls run under their credentials rather than a shared key.
- 03Decide which messages, conversations and participants 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 MSG91 integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an MSG91 integration without building it. Your customers connect their own MSG91 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 an MSG91 update is not your on-call problem.
- One integration serves your product and your agents. The same governed MSG91 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
Slack
Microsoft Teams
TwilioOften used alongside
Tools the same teams tend to run next to MSG91, across other categories.
Aircall
Calendly
Gong
Google CalendarMSG91 integration FAQ
How do I add an MSG91 integration to my product?
Enable the MSG91 connector in your fastn dashboard, then let each customer authenticate their own MSG91 account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no MSG91 client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own MSG91 account?
Yes. Every connection is scoped to the individual customer, so each authorises their own MSG91 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 MSG91 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 send only from templates a tenant has pre-approved, since unregistered templates will not deliver
Who maintains the MSG91 integration?
fastn does. When MSG91 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 MSG91 account?
Yes. Every customer authorises their own MSG91 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 MSG91 integration?
A common starting point: let a customer connect their own MSG91 account so messages are sent under their sender ID and DLT registration. 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 MSG91 integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding MSG91 does not change your per-connector cost. You can start free with 3 connected accounts.
Add MSG91 to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.