# How to connect SMS Alert to OpenClaw (paste one key, 23 tools) > Connect SMS Alert to OpenClaw with ClawLink: paste your SMS Alert key once and 23 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/sms-alert The usual route to SMS Alert access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical SMS Alert setup: install one ClawHub skill, connect SMS Alert in the browser, and OpenClaw can call real SMS Alert actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to SMS Alert. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect SMS Alert** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect sms-alert # connect SMS Alert (browser OAuth) npx -y @useclawlink/cli actions sms-alert # list available actions npx -y @useclawlink/cli run sms-alert --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect SMS Alert in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your SMS Alert API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from SMS Alert, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once SMS Alert is connected in the dashboard, that agent calls the same 23 SMS Alert tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## SMS Alert MCP for OpenClaw Looking for a SMS Alert MCP server for OpenClaw? ClawLink connects SMS Alert to OpenClaw and exposes 23 SMS Alert tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes SMS Alert integration](https://claw-link.dev/hermes/sms-alert) works the same way. ## What the OpenClaw SMS Alert integration can do 23 SMS Alert tools are ready for OpenClaw once the account is connected. The 19 below are the ones people reach for most; your agent can call all 23. ### 19 of 23 SMS Alert tools for OpenClaw | Tool | What it does | |---|---| | **Get balance check** `sms_alert_get_balance_check` | Retrieve the current SMS credit balance | | **Get delivery report** `sms_alert_get_delivery_report` | Retrieve delivery report for sent SMS messages by batch ID | | **Get group detail** `sms_alert_get_group_detail` | Retrieve details of a specific SMS Alert group | | **Get group list** `sms_alert_get_group_list` | Retrieve a list of SMS Alert groups | | **Get sender ID list** `sms_alert_get_sender_id_list` | Fetch the list of available sender IDs | | **Get template list** `sms_alert_get_template_list` | Retrieve list of SMS templates from your SmsAlert account | | **Get user profile** `sms_alert_get_user_profile` | Retrieve user login and profile information | | **Post sent sms report** `sms_alert_post_sent_sms_report` | Retrieve SMS campaign sent report details | | **Change password** `sms_alert_change_password` | Change the password for the authenticated user account | | **Post create contact** `sms_alert_post_create_contact` | Create New Contact | | **Post create group** `sms_alert_post_create_group` | Create a new contact group | | **Post create short URL** `sms_alert_post_create_short_url` | Create a short URL for a given long URL | | **Post create template** `sms_alert_post_create_template` | Create a new SMS template | | **Post edit contact** `sms_alert_post_edit_contact` | Edit an existing contact’s details | | **Post edit group** `sms_alert_post_edit_group` | Edit an existing group\u0019s name | | **Post edit profile** `sms_alert_post_edit_profile` | Update user account profile details | | **Post edit template** `sms_alert_post_edit_template` | Edit an existing SMS template | | **Post generate otp** `sms_alert_post_generate_otp` | Generate a one-time password (OTP) | | **Send sms xml** `sms_alert_send_sms_xml` | Send SMS messages using XML format for bulk sending | ## Example prompts **Get Balance Check** > Pull the relevant data from SMS Alert, summarize it in plain English, and point out anything that needs attention. **Get Delivery Report** > Pull the relevant data from SMS Alert, summarize it in plain English, and point out anything that needs attention. **Get Group Detail** > Pull the relevant data from SMS Alert, summarize it in plain English, and point out anything that needs attention. **Get Group List** > Pull the relevant data from SMS Alert, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want SMS Alert working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the SMS Alert API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected SMS Alert account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for SMS Alert. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right SMS Alert actions to the runtime in a format your agent can reliably use. | 23 tools for SMS Alert are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes SMS Alert to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect SMS Alert in the browser, and the 23 tools above work from chat. There is no SDK and no config file, and the SMS Alert key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the SMS Alert skill but can't call the tools The ClawHub skill teaches OpenClaw about SMS Alert, but the calls run through the ClawLink plugin and your connected account. Make sure SMS Alert is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect SMS Alert from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling SMS Alert tools SMS Alert tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every SMS Alert call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### SMS Alert returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for SMS Alert has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw SMS Alert integration? Yes. ClawLink is the fastest way to connect OpenClaw to SMS Alert: link your SMS Alert account once in the browser and OpenClaw can call the SMS Alert API through 23 ready-made tools — no custom code or token handling. ### How do I add SMS Alert to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink SMS Alert skill from ClawHub, then you click Connect in the dashboard to authorize SMS Alert. OpenClaw calls the tools from the next message — no config files, and the SMS Alert key you paste is stored server-side instead of in your environment. ### How long does it take to connect SMS Alert to OpenClaw? About two minutes. Sign in, click Connect next to SMS Alert in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring SMS Alert up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want SMS Alert working from chat. ### OpenClaw installed the SMS Alert skill but can't call the tools The ClawHub skill teaches OpenClaw about SMS Alert, but the calls run through the ClawLink plugin and your connected account. Make sure SMS Alert is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Connect SendGrid](https://claw-link.dev/openclaw/sendgrid) — Deliver transactional and marketing emails - [OpenClaw Dialpad integration](https://claw-link.dev/openclaw/dialpad) — Business phone, messaging, and video conferencing - [OpenClaw Discord Bot integration](https://claw-link.dev/openclaw/discord-bot) — Automate Discord server actions with bot-specific permissions