How to connect Jotform to OpenClaw
Connect Jotform to OpenClaw with ClawLink: paste your Jotform key once and 18 tools work from chat. No MCP server to run, nothing stored on your machine.
JotformAPI KEYMCPCreate forms, manage submissions, and build workflows. Once connected, OpenClaw can read and act on Jotform from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Jotform 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 Jotform setup: install one ClawHub skill, connect Jotform in the browser, and OpenClaw can call real Jotform actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Jotform skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Jotform" (hith3sh/jotform-forms) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/jotform-forms
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Jotform.
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 Jotform
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Jotform?"
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 Jotform in the ClawLink dashboard — paste your Jotform API key once.
Verify the connection by asking OpenClaw:
Use Jotform to clone form 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Jotform is connected in the dashboard, that agent calls the same 18 Jotform tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Jotform MCP for OpenClaw
Looking for a Jotform MCP server for OpenClaw? ClawLink connects Jotform to OpenClaw and exposes 18 Jotform tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Jotform integration works the same way.
What the OpenClaw Jotform integration can do
18 Jotform 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 18.
17 of 18 Jotform tools for OpenClaw
| Tool | What it does |
|---|---|
Clone form jotform_clone_form | Tool to clone a single form in Jotform. Creates a complete copy of the form with all its questions and settings. Use when you need to duplicate an existing form. |
Create label jotform_create_label | Tool to create a new label for organizing forms in Jotform. Use when you need to categorize or group forms with a named label. |
Get label jotform_get_label | Tool to retrieve details of a label by its ID, including name and color. Use when you need to fetch information about a specific label. |
Get label resources jotform_get_label_resources | Tool to get a list of assets (forms) in a label and their associated information. Use when you need to retrieve forms organized under a specific label. |
Get system plan jotform_get_system_plan | Tool to retrieve details of a specific system plan. Use when you need to check limits and pricing of a plan. |
Get user details jotform_get_user_details | Tool to retrieve details of the authenticated user, including account and usage info. Use after confirming valid API key. |
Get user folders jotform_get_user_folders | Tool to retrieve a list of labels (folders replacement) for the authenticated user. Uses the GET /user/labels endpoint per Jotform's migration from folders to labels. |
Get user forms jotform_get_user_forms | Tool to retrieve a list of forms created by the authenticated user. Use after setting up API key authentication. |
Get user history jotform_get_user_history | Tool to fetch user activity history records. Use when auditing or filtering user actions by type or date. |
Get user reports jotform_get_user_reports | Tool to retrieve list of report URLs for all forms in the account. Includes Excel, CSV, printable charts, and embeddable HTML tables. |
Get user settings jotform_get_user_settings | Tool to retrieve the settings of the authenticated user. Use after confirming a valid API key. |
Get user settings by key jotform_get_user_settings_by_key | Retrieve a specific user setting by key |
Get user submissions jotform_get_user_submissions | Retrieve all submissions for all forms on the account |
Get user usage jotform_get_user_usage | Retrieve monthly usage statistics for the authenticated user |
Update label jotform_update_label | Update an existing label with new name or color settings |
Update user settings jotform_update_user_settings | Update user's settings like time zone, language, email, and website |
Remove label resources jotform_remove_label_resources | Remove specified resources (forms) from a label by their IDs and types |
Try it: find the Jotform tool you need
Browse the 17 Jotform tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Jotform to clone form and walk me through the result in plain English.
Create it in Jotform for me, then confirm the important fields before you finish.
Pull the relevant data from Jotform, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Jotform, 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 Jotform working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Jotform API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Jotform 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 Jotform. | 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 Jotform actions to the runtime in a format your agent can reliably use. | 18 tools for Jotform are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Jotform 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 Jotform in the browser, and the 18 tools above work from chat. There is no SDK and no config file, and the Jotform 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 Jotform skill but can't call the tools
The ClawHub skill teaches OpenClaw about Jotform, but the calls run through the ClawLink plugin and your connected account. Make sure Jotform 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 Jotform 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 Jotform tools
Jotform 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 Jotform 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.
Jotform 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 Jotform 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 Jotform integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Jotform: link your Jotform account once in the browser and OpenClaw can call the Jotform API through 18 ready-made tools — no custom code or token handling.
How do I add Jotform to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Jotform skill from ClawHub, then you click Connect in the dashboard to authorize Jotform. OpenClaw calls the tools from the next message — no config files, and the Jotform key you paste is stored server-side instead of in your environment.
How long does it take to connect Jotform to OpenClaw?
About two minutes. Sign in, click Connect next to Jotform in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Jotform 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 Jotform working from chat.
OpenClaw installed the Jotform skill but can't call the tools
The ClawHub skill teaches OpenClaw about Jotform, but the calls run through the ClawLink plugin and your connected account. Make sure Jotform 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.
