Msg91
for LuumenAI
Check campaign delivery in Segmento, then send SMS and OTP with approval
Connect Msg91 and your agent can read what your messaging is actually doing: which campaigns are running in Segmento, which event types are configured, and which user events failed. When a message needs to go out, it sends SMS through a Flow template or issues an OTP as a previewed, approved step. Authentication is by API key.
The Msg91 toolbox
8 tools: 3 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Event TypesRetrieves all event types configured in MSG91 Segmento.
- ReadGet Failed EventsRetrieve failed user events from a MSG91 Segmento campaign.
- ReadList CampaignsList all campaigns in Segmento.
- WriteCreate User EventsCreate and track user events in MSG91 Segmento for customer behavior analysis and segmentation. Approval by default
- WriteResend OTPResend OTP to the same mobile number via text message or voice call. Approval by default
- WriteSend OTPSend OTP (One-Time Password) to a mobile number using a pre-configured MSG91 template. Approval by default
- WriteSend SMS via Flow (V5)Send SMS messages using pre-defined templates via MSG91 Flow API v5. Approval by default
- WriteVerify OTPVerify an OTP (One-Time Password) sent to a mobile number. Approval by default
One prompt, start to finish
What a governed Msg91 run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create user events, resend otp, send otp, send sms via flow (v5), and more — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Msg91 — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut Msg91 to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.