Use Msg91 from Claude
Add the Msg91 connection to a Space that runs Claude, then use it from every channel in that Space.
Create a Msg91 connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Msg91 connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Msg91 connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Msg91 sends SMS, WhatsApp, email, and voice messages, and its Segmento tool tracks user behavior for campaigns and OTP delivery. From a type.com thread, a growth or support team can ask Claude to log a user event, check why a campaign failed, or resend a one-time code to a customer.
Connect Msg91 once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Record a user action, like a signup or purchase, as an event in Msg91 Segmento so it can be used later to build a targeted campaign.
Log a purchase event in Msg91 for user ID 8821 so we can segment buyers for next week's campaign.
Pull the failed events for a campaign to see which recipients were skipped and why, instead of guessing at delivery problems.
Check the failed events for our last Msg91 campaign and tell me the most common error reason.
Send a new OTP to the same number when a customer says the original code expired or never arrived.
Resend the OTP to this customer's number in Msg91, they said the first one never came through.
Records a user action, such as a purchase or signup, in Msg91 Segmento for later use in segmentation.
Lists the event types already configured in Msg91 Segmento, useful for seeing what can be tracked.
Returns events that failed during a campaign, helping identify delivery errors or invalid recipients.
Returns a paginated list of Segmento campaigns, useful for finding a specific one to inspect further.
Sends a new one-time code to the same number by text or voice when the original was not received.
MSG91 documents cloud communication APIs across SMS, WhatsApp, email, voice, OTP, templates, contacts, campaigns, and transactional messaging. Integrations can send and track messages across channels, manage approved templates, and connect customer-communication workflows with API-key authenticated requests.
Yes. With a Msg91 connection shared to a type.com Space, Claude can check failed events, list campaigns, and resend an OTP, and the team can follow the same investigation in the thread.
Msg91 uses an API key, added once by an admin when the connection is created. Any Space that connection is shared with can use it without handling the key.
Yes. A recurring task, such as checking for failed events after each send, can be set up as a type.com automation that reports to a channel.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect Kickbox to Claude in type.com to check disposable addresses and verify emails before they hit your outreach list.
Connect Listclean to Claude in type.com to verify email lists and download clean results in a shared thread.
Connect Loops.so to Claude in type.com to create, find, and clean up SaaS email contacts and properties from shared threads.
Connect Mailboxlayer to Claude in type.com to check email syntax, domain, and SMTP validity in a shared thread.