# How to connect Softr to OpenClaw (paste one key, 21 tools) > Connect Softr to OpenClaw with ClawLink: paste your Softr key once and 21 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/softr The usual route to Softr 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 Softr setup: install one ClawHub skill, connect Softr in the browser, and OpenClaw can call real Softr 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 Softr. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Softr** — 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 softr # connect Softr (browser OAuth) npx -y @useclawlink/cli actions softr # list available actions npx -y @useclawlink/cli run softr --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 Softr in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Softr API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Softr, 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 Softr is connected in the dashboard, that agent calls the same 21 Softr 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). ## Softr MCP for OpenClaw Looking for a Softr MCP server for OpenClaw? ClawLink connects Softr to OpenClaw and exposes 21 Softr 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 Softr integration](https://claw-link.dev/hermes/softr) works the same way. ## What the OpenClaw Softr integration can do 21 Softr tools are ready for OpenClaw once the account is connected. The 17 below are the ones people reach for most; your agent can call all 21. ### 17 of 21 Softr tools for OpenClaw | Tool | What it does | |---|---| | **Get database** `softr_get_database` | Retrieve details for a specific database by ID | | **Get databases** `softr_get_databases` | Retrieve all databases available in the workspace | | **Get record** `softr_get_record` | Retrieve a single record by its ID from a Softr database table | | **Get records** `softr_get_records` | Retrieve a paginated list of records from a Softr table | | **Get table** `softr_get_table` | Retrieve details for a specific table by ID | | **Get table field** `softr_get_table_field` | Retrieve a specific field from a Softr table by field ID | | **Get table views** `softr_get_table_views` | Retrieve all views for a specified table in a Softr database | | **Get tables** `softr_get_tables` | Retrieves all tables within a specified Softr database | | **Search records** `softr_search_records` | Search records in a Softr database table with filtering and pagination | | **Create database** `softr_create_database` | Create a new database in a Softr workspace | | **Create record** `softr_create_record` | Creates a new record in a Softr database table | | **Create table** `softr_create_table` | Create a new table within a specified Softr database | | **Create table field** `softr_create_table_field` | Add a new field to a Softr table | | **Update database** `softr_update_database` | Update an existing database's name and/or description | | **Update record** `softr_update_record` | Update an existing record's field values in a Softr table | | **Update table** `softr_update_table` | Update a table's name and/or description in Softr Database | | **Update table field** `softr_update_table_field` | Updates an existing field in a Softr table | ## Example prompts **Get Database** > Pull the relevant data from Softr, summarize it in plain English, and point out anything that needs attention. **Get Databases** > Pull the relevant data from Softr, summarize it in plain English, and point out anything that needs attention. **Get Record** > Pull the relevant data from Softr, summarize it in plain English, and point out anything that needs attention. **Get Records** > Pull the relevant data from Softr, 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 Softr working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Softr API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Softr 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 Softr. | 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 Softr actions to the runtime in a format your agent can reliably use. | 21 tools for Softr are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Softr 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 Softr in the browser, and the 21 tools above work from chat. There is no SDK and no config file, and the Softr 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 Softr skill but can't call the tools The ClawHub skill teaches OpenClaw about Softr, but the calls run through the ClawLink plugin and your connected account. Make sure Softr 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 Softr 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 Softr tools Softr 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 Softr 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. ### Softr 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 Softr has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Softr integration? Yes. ClawLink is the fastest way to connect OpenClaw to Softr: link your Softr account once in the browser and OpenClaw can call the Softr API through 21 ready-made tools — no custom code or token handling. ### How do I add Softr to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Softr skill from ClawHub, then you click Connect in the dashboard to authorize Softr. OpenClaw calls the tools from the next message — no config files, and the Softr key you paste is stored server-side instead of in your environment. ### How long does it take to connect Softr to OpenClaw? About two minutes. Sign in, click Connect next to Softr in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Softr 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 Softr working from chat. ### OpenClaw installed the Softr skill but can't call the tools The ClawHub skill teaches OpenClaw about Softr, but the calls run through the ClawLink plugin and your connected account. Make sure Softr 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 - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](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.