# How to connect Svix to OpenClaw (paste one key, 37 tools) > Connect Svix to OpenClaw with ClawLink: paste your Svix key once and 37 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/svix The usual route to Svix 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 Svix setup: install one ClawHub skill, connect Svix in the browser, and OpenClaw can call real Svix 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 Svix. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Svix** — 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 svix # connect Svix (browser OAuth) npx -y @useclawlink/cli actions svix # list available actions npx -y @useclawlink/cli run svix --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 Svix in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Svix API key once. Verify the connection by asking OpenClaw: > Use Svix to app get and walk me through the result in plain English. ### 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 Svix is connected in the dashboard, that agent calls the same 37 Svix 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). ## Svix MCP for OpenClaw Looking for a Svix MCP server for OpenClaw? ClawLink connects Svix to OpenClaw and exposes 37 Svix 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 Svix integration](https://claw-link.dev/hermes/svix) works the same way. ## What the OpenClaw Svix integration can do 37 Svix tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 37. ### 30 of 37 Svix tools for OpenClaw | Tool | What it does | |---|---| | **App get** `svix_app_get` | Retrieve details of a specific Svix application by its ID | | **App list** `svix_app_list` | List all applications | | **Attempt get** `svix_attempt_get` | Retrieve details of a specific message attempt | | **Attempt list** `svix_attempt_list` | List all delivery attempts for a specific message | | **Endpoint get** `svix_endpoint_get` | Retrieve details of a specific endpoint | | **Endpoint list** `svix_endpoint_list` | List all endpoints for a specific application | | **Endpoint secret get** `svix_endpoint_secret_get` | Retrieve the secret for a specific endpoint | | **Endpoint stats get** `svix_endpoint_stats_get` | Retrieve basic statistics for a specific endpoint | | **Endpoint transformation get** `svix_endpoint_transformation_get` | Retrieve transformation settings for a specific endpoint | | **Event type get** `svix_event_type_get` | Retrieve details of a specific event type by its name | | **Event type list** `svix_event_type_list` | Retrieve a list of all event types | | **Integration get** `svix_integration_get` | Retrieve details of a specific integration | | **Integration list** `svix_integration_list` | List all integrations for a specific application | | **Message get** `svix_message_get` | Retrieve details of a specific message by its ID | | **Message list** `svix_message_list` | List all messages for a specific application | | **App create** `svix_app_create` | Create a new Svix application | | **App update** `svix_app_update` | Update an existing Svix application by ID | | **Endpoint create** `svix_endpoint_create` | Create a new Svix webhook endpoint | | **Endpoint patch** `svix_endpoint_patch` | Partially update an endpoint’s configuration | | **Endpoint patch headers** `svix_endpoint_patch_headers` | Partially update headers for a specific endpoint | | **Endpoint recover failed webhooks** `svix_endpoint_recover_failed_webhooks` | Recover messages that failed to send to an endpoint | | **Endpoint replay missing** `svix_endpoint_replay_missing` | Replay missing webhooks for a specific endpoint | | **Endpoint send example message** `svix_endpoint_send_example_message` | Send a test message for a specific event type to an endpoint | | **Endpoint transformation set** `svix_endpoint_transformation_set` | Set or update transformation settings for an endpoint | | **Endpoint update** `svix_endpoint_update` | Update an existing endpoint or create it if it doesn't exist (upsert) | | **Endpoint update headers** `svix_endpoint_update_headers` | Completely replace headers for a specific endpoint | | **Event type create** `svix_event_type_create` | Create a new event type in Svix or unarchive an existing one | | **Event type update** `svix_event_type_update` | Update an existing event type's description, schema, feature flags, or archive status | | **Integration create** `svix_integration_create` | Create a new integration for a specific application | | **Integration update** `svix_integration_update` | Update an existing integration by ID | ## Example prompts **App Get** > Use Svix to app get and walk me through the result in plain English. **App List** > Use Svix to app list and walk me through the result in plain English. **Attempt Get** > Use Svix to attempt get and walk me through the result in plain English. **Attempt List** > Use Svix to attempt list and walk me through the result in plain English. ## 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 Svix working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Svix API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Svix 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 Svix. | 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 Svix actions to the runtime in a format your agent can reliably use. | 37 tools for Svix are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Svix 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 Svix in the browser, and the 37 tools above work from chat. There is no SDK and no config file, and the Svix 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 Svix skill but can't call the tools The ClawHub skill teaches OpenClaw about Svix, but the calls run through the ClawLink plugin and your connected account. Make sure Svix 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 Svix 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 Svix tools Svix 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 Svix 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. ### Svix 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 Svix has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Svix integration? Yes. ClawLink is the fastest way to connect OpenClaw to Svix: link your Svix account once in the browser and OpenClaw can call the Svix API through 37 ready-made tools — no custom code or token handling. ### How do I add Svix to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Svix skill from ClawHub, then you click Connect in the dashboard to authorize Svix. OpenClaw calls the tools from the next message — no config files, and the Svix key you paste is stored server-side instead of in your environment. ### How long does it take to connect Svix to OpenClaw? About two minutes. Sign in, click Connect next to Svix in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Svix 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 Svix working from chat. ### OpenClaw installed the Svix skill but can't call the tools The ClawHub skill teaches OpenClaw about Svix, but the calls run through the ClawLink plugin and your connected account. Make sure Svix 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 - [GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.