How to connect Supersaas to OpenClaw
Connect Supersaas to OpenClaw with ClawLink: paste your Supersaas key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.
SupersaasAPI KEYMCPAppointment Scheduling for Every Situation.. Once connected, OpenClaw can read and act on Supersaas from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Supersaas 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 Supersaas setup: install one ClawHub skill, connect Supersaas in the browser, and OpenClaw can call real Supersaas 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 Supersaas.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Supersaas
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Supersaas?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Supersaas in the ClawLink dashboard — paste your Supersaas API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Supersaas, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Supersaas is connected in the dashboard, that agent calls the same 10 Supersaas tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Supersaas MCP for OpenClaw
Looking for a Supersaas MCP server for OpenClaw? ClawLink connects Supersaas to OpenClaw and exposes 10 Supersaas tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Supersaas integration works the same way.
What the OpenClaw Supersaas integration can do
10 Supersaas tools are ready for OpenClaw once the account is connected. The 9 below are the ones people reach for most; your agent can call all 10.
9 of 10 Supersaas tools for OpenClaw
| Tool | What it does |
|---|---|
Get user supersaas_get_user | Read a single user by ID from SuperSaaS |
List field list supersaas_list_field_list | Retrieve available fields on Schedule or User objects |
List groups supersaas_list_groups | Retrieve all user groups defined in a SuperSaaS account |
List promotions supersaas_list_promotions | List all promotional coupon codes in the account or retrieve a single promotion by code |
List schedules supersaas_list_schedules | Retrieve all schedules in a SuperSaaS account with their IDs and names |
List super forms supersaas_list_super_forms | Retrieve all form definitions in a SuperSaaS account with their IDs and names |
List users supersaas_list_users | List all users in the SuperSaaS account |
Create user supersaas_create_user | Create a new user in SuperSaaS |
Update user supersaas_update_user | Update an existing SuperSaaS user by ID |
Try it: find the Supersaas tool you need
Browse the 9 Supersaas tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Supersaas, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Supersaas, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Supersaas, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Supersaas, group them by priority, and recommend what OpenClaw should do next.
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 Supersaas working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Supersaas API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Supersaas 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 Supersaas. | 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 Supersaas actions to the runtime in a format your agent can reliably use. | 10 tools for Supersaas are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Supersaas 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 Supersaas in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Supersaas key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Supersaas skill but can't call the tools
The ClawHub skill teaches OpenClaw about Supersaas, but the calls run through the ClawLink plugin and your connected account. Make sure Supersaas 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 Supersaas 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 Supersaas tools
Supersaas 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 Supersaas 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.
Supersaas 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 Supersaas has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Supersaas integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Supersaas: link your Supersaas account once in the browser and OpenClaw can call the Supersaas API through 10 ready-made tools — no custom code or token handling.
How do I add Supersaas to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Supersaas skill from ClawHub, then you click Connect in the dashboard to authorize Supersaas. OpenClaw calls the tools from the next message — no config files, and the Supersaas key you paste is stored server-side instead of in your environment.
How long does it take to connect Supersaas to OpenClaw?
About two minutes. Sign in, click Connect next to Supersaas in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Supersaas 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 Supersaas working from chat.
OpenClaw installed the Supersaas skill but can't call the tools
The ClawHub skill teaches OpenClaw about Supersaas, but the calls run through the ClawLink plugin and your connected account. Make sure Supersaas 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.
