# How to connect Formdesk to OpenClaw (paste one key, 20 tools) > Connect Formdesk to OpenClaw with ClawLink: paste your Formdesk key once and 20 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/formdesk The usual route to Formdesk 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 Formdesk setup: install one ClawHub skill, connect Formdesk in the browser, and OpenClaw can call real Formdesk 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 Formdesk. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Formdesk** — 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 formdesk # connect Formdesk (browser OAuth) npx -y @useclawlink/cli actions formdesk # list available actions npx -y @useclawlink/cli run formdesk --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 Formdesk in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Formdesk API key once. Verify the connection by asking OpenClaw: > Use Formdesk to automatic login 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 Formdesk is connected in the dashboard, that agent calls the same 20 Formdesk 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). ## Formdesk MCP for OpenClaw Looking for a Formdesk MCP server for OpenClaw? ClawLink connects Formdesk to OpenClaw and exposes 20 Formdesk 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 Formdesk integration](https://claw-link.dev/hermes/formdesk) works the same way. ## What the OpenClaw Formdesk integration can do 20 Formdesk tools are ready for OpenClaw once the account is connected. The 16 below are the ones people reach for most; your agent can call all 20. ### 16 of 20 Formdesk tools for OpenClaw | Tool | What it does | |---|---| | **Automatic login** `formdesk_automatic_login` | Validates the Formdesk API bearer token and returns authentication details | | **Get field details** `formdesk_get_field_details` | Retrieves comprehensive details about a specific field in a Formdesk form | | **Get form details** `formdesk_get_form_details` | Retrieves comprehensive details about a specific Formdesk form by its ID | | **Get form fields** `formdesk_get_form_fields` | Retrieve all fields of a specific form | | **Get form list** `formdesk_get_form_list` | Retrieve a list of all forms in the Formdesk account | | **Get form visitors** `formdesk_get_form_visitors` | Retrieves all visitors registered to access a specific Formdesk form | | **Get visitor details** `formdesk_get_visitor_details` | Retrieve complete details of a specific visitor in a Formdesk form | | **Kvk handelsregister lookup** `formdesk_kvk_handelsregister_lookup` | Lookup company details from the Dutch KVK Handelsregister | | **Manage visitor entries** `formdesk_manage_visitor_entries` | Retrieve form entries (submissions) from a Formdesk form | | **Create entry** `formdesk_create_entry` | Submit a new entry (result) to a Formdesk form | | **Create field** `formdesk_create_field` | Creates a new field in a Formdesk form | | **Create visitor** `formdesk_create_visitor` | Add a new visitor to a specific Formdesk form | | **Multiple pages form** `formdesk_multiple_pages_form` | Create a multi-page Formdesk form | | **Update field** `formdesk_update_field` | Updates properties of an existing field in a Formdesk form | | **Update form** `formdesk_update_form` | Updates properties of an existing form in Formdesk | | **Update visitor** `formdesk_update_visitor` | Update an existing visitor's attributes in a Formdesk form | ## Example prompts **Automatic Login** > Use Formdesk to automatic login and walk me through the result in plain English. **Get Field Details** > Pull the relevant data from Formdesk, summarize it in plain English, and point out anything that needs attention. **Get Form Details** > Pull the relevant data from Formdesk, summarize it in plain English, and point out anything that needs attention. **Get Form Fields** > Pull the relevant data from Formdesk, 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 Formdesk working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Formdesk API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Formdesk 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 Formdesk. | 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 Formdesk actions to the runtime in a format your agent can reliably use. | 20 tools for Formdesk are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Formdesk 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 Formdesk in the browser, and the 20 tools above work from chat. There is no SDK and no config file, and the Formdesk 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 Formdesk skill but can't call the tools The ClawHub skill teaches OpenClaw about Formdesk, but the calls run through the ClawLink plugin and your connected account. Make sure Formdesk 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 Formdesk 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 Formdesk tools Formdesk 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 Formdesk 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. ### Formdesk 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 Formdesk has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Formdesk integration? Yes. ClawLink is the fastest way to connect OpenClaw to Formdesk: link your Formdesk account once in the browser and OpenClaw can call the Formdesk API through 20 ready-made tools — no custom code or token handling. ### How do I add Formdesk to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Formdesk skill from ClawHub, then you click Connect in the dashboard to authorize Formdesk. OpenClaw calls the tools from the next message — no config files, and the Formdesk key you paste is stored server-side instead of in your environment. ### How long does it take to connect Formdesk to OpenClaw? About two minutes. Sign in, click Connect next to Formdesk in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Formdesk 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 Formdesk working from chat. ### OpenClaw installed the Formdesk skill but can't call the tools The ClawHub skill teaches OpenClaw about Formdesk, but the calls run through the ClawLink plugin and your connected account. Make sure Formdesk 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 - [SafetyCulture tools](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.