How to connect Renderform to OpenClaw
Connect Renderform to OpenClaw with ClawLink: paste your Renderform key once and 7 tools work from chat. No MCP server to run, nothing stored on your machine.
RenderformAPI KEYMCPRenderForm is a user-friendly automation and design tool that enables the creation of templates and images with custom content such as images, texts, and QR codes.. Once connected, OpenClaw can read and act on Renderform from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Renderform 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 Renderform setup: install one ClawHub skill, connect Renderform in the browser, and OpenClaw can call real Renderform 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 Renderform.
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 Renderform
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Renderform?"
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 Renderform in the ClawLink dashboard — paste your Renderform API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Renderform, 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 Renderform is connected in the dashboard, that agent calls the same 7 Renderform tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Renderform MCP for OpenClaw
Looking for a Renderform MCP server for OpenClaw? ClawLink connects Renderform to OpenClaw and exposes 7 Renderform tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Renderform integration works the same way.
What the OpenClaw Renderform integration can do
7 Renderform tools are ready for OpenClaw once the account is connected. The 6 below are the ones people reach for most; your agent can call all 7.
6 of 7 Renderform tools for OpenClaw
| Tool | What it does |
|---|---|
Get result renderform_get_result | Retrieve detailed information about a specific render result by its identifier |
List fonts renderform_list_fonts | Retrieve all available fonts including Google Fonts and custom uploaded fonts |
List results v2 renderform_list_results_v2 | List all rendered images and PDFs with pagination support |
List templates v2 renderform_list_templates_v2 | Get a list of all your templates with metadata and preview links |
Create PDF from URL renderform_create_pdf_from_url | Create a PDF from any website URL with customizable page format and auto-expiration |
Take screenshot renderform_take_screenshot | Capture a screenshot of a website with given dimensions |
Try it: find the Renderform tool you need
Browse the 6 Renderform 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 Renderform, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Renderform, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Renderform, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Renderform, 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 Renderform working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Renderform API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Renderform 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 Renderform. | 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 Renderform actions to the runtime in a format your agent can reliably use. | 7 tools for Renderform are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Renderform 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 Renderform in the browser, and the 7 tools above work from chat. There is no SDK and no config file, and the Renderform 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 Renderform skill but can't call the tools
The ClawHub skill teaches OpenClaw about Renderform, but the calls run through the ClawLink plugin and your connected account. Make sure Renderform 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 Renderform 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 Renderform tools
Renderform 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 Renderform 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.
Renderform 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 Renderform 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 Renderform integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Renderform: link your Renderform account once in the browser and OpenClaw can call the Renderform API through 7 ready-made tools — no custom code or token handling.
How do I add Renderform to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Renderform skill from ClawHub, then you click Connect in the dashboard to authorize Renderform. OpenClaw calls the tools from the next message — no config files, and the Renderform key you paste is stored server-side instead of in your environment.
How long does it take to connect Renderform to OpenClaw?
About two minutes. Sign in, click Connect next to Renderform in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Renderform 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 Renderform working from chat.
OpenClaw installed the Renderform skill but can't call the tools
The ClawHub skill teaches OpenClaw about Renderform, but the calls run through the ClawLink plugin and your connected account. Make sure Renderform 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 tools
Manage repositories, issues, pull requests, and workflows
OpenClaw PagerDuty integration
Manage incidents, on-call schedules, and services
OpenClaw SafetyCulture integration
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.