# How to connect Templated to OpenClaw (paste one key, 30 tools) > Connect Templated to OpenClaw with ClawLink: paste your Templated key once and 30 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/templated The usual route to Templated 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 Templated setup: install one ClawHub skill, connect Templated in the browser, and OpenClaw can call real Templated 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 Templated. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Templated** — 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 templated # connect Templated (browser OAuth) npx -y @useclawlink/cli actions templated # list available actions npx -y @useclawlink/cli run templated --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 Templated in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Templated API key once. Verify the connection by asking OpenClaw: > Use Templated to count template clones 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 Templated is connected in the dashboard, that agent calls the same 30 Templated 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). ## Templated MCP for OpenClaw Looking for a Templated MCP server for OpenClaw? ClawLink connects Templated to OpenClaw and exposes 30 Templated 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 Templated integration](https://claw-link.dev/hermes/templated) works the same way. ## What the OpenClaw Templated integration can do 30 Templated tools are ready for OpenClaw once the account is connected. The 27 below are the ones people reach for most; your agent can call all 30. ### 27 of 30 Templated tools for OpenClaw | Tool | What it does | |---|---| | **Count template clones** `templated_count_template_clones` | Get the count of cloned templates for a specific source template | | **Get account information** `templated_get_account_information` | Retrieve account information, including email, name, team name, API usage statistics, and | | **List all templates** `templated_list_all_templates` | List all templates of a user | | **List folder renders** `templated_list_folder_renders` | List all renders in a specific folder | | **List folder templates** `templated_list_folder_templates` | List all templates in a specific folder | | **List folders** `templated_list_folders` | List all folders in the account | | **List fonts** `templated_list_fonts` | List all available fonts including Google Fonts and user-uploaded custom fonts | | **List gallery templates** `templated_list_gallery_templates` | List templates from the public gallery | | **List renders** `templated_list_renders` | List all renders in the account | | **List template clones** `templated_list_template_clones` | List all cloned templates in the account | | **List template renders** `templated_list_template_renders` | List all renders of a specific template | | **List uploads** `templated_list_uploads` | List all uploaded images in the account | | **Merge renders** `templated_merge_renders` | Merge multiple renders into a single PDF output | | **Retrieve render** `templated_retrieve_render` | Retrieve details of a specific render by its ID | | **Retrieve template** `templated_retrieve_template` | Retrieve a single Template by its unique ID | | **Add tags to template** `templated_add_tags_to_template` | Append new tags to an existing template without overwriting existing tags | | **Clone template action** `templated_clone_template_action` | Clone an existing template | | **Create folder** `templated_create_folder` | Create a new folder for organizing templates and renders | | **Create render** `templated_create_render` | Create document renders from templates | | **Create template** `templated_create_template` | Create a new template with specified dimensions and layers | | **Duplicate render** `templated_duplicate_render` | Duplicate an existing render with the same settings and template | | **Move render to folder** `templated_move_render_to_folder` | Move a render to a specific folder | | **Move template to folder** `templated_move_template_to_folder` | Move a template to a folder | | **Update folder** `templated_update_folder` | Update an existing folder's properties | | **Update template** `templated_update_template` | Update an existing template including its properties and layers | | **Update template tags** `templated_update_template_tags` | Overwrite all tags on a template | | **Remove template tags** `templated_remove_template_tags` | Remove specific tags from a template | ## Example prompts **Count Template Clones** > Use Templated to count template clones and walk me through the result in plain English. **Get Account Information** > Pull the relevant data from Templated, summarize it in plain English, and point out anything that needs attention. **List All Templates** > List the relevant items in Templated, group them by priority, and recommend what OpenClaw should do next. **List Folder Renders** > List the relevant items in Templated, 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 Templated working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Templated API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Templated 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 Templated. | 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 Templated actions to the runtime in a format your agent can reliably use. | 30 tools for Templated are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Templated 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 Templated in the browser, and the 30 tools above work from chat. There is no SDK and no config file, and the Templated 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 Templated skill but can't call the tools The ClawHub skill teaches OpenClaw about Templated, but the calls run through the ClawLink plugin and your connected account. Make sure Templated 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 Templated 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 Templated tools Templated 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 Templated 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. ### Templated 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 Templated has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Templated integration? Yes. ClawLink is the fastest way to connect OpenClaw to Templated: link your Templated account once in the browser and OpenClaw can call the Templated API through 30 ready-made tools — no custom code or token handling. ### How do I add Templated to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Templated skill from ClawHub, then you click Connect in the dashboard to authorize Templated. OpenClaw calls the tools from the next message — no config files, and the Templated key you paste is stored server-side instead of in your environment. ### How long does it take to connect Templated to OpenClaw? About two minutes. Sign in, click Connect next to Templated in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Templated 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 Templated working from chat. ### OpenClaw installed the Templated skill but can't call the tools The ClawHub skill teaches OpenClaw about Templated, but the calls run through the ClawLink plugin and your connected account. Make sure Templated 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 Cloudinary integration](https://claw-link.dev/openclaw/cloudinary) — Cloudinary is a cloud-based media management platform for uploading, storing, transforming, and delivering images and videos via CDN. - [Penpot](https://claw-link.dev/openclaw/penpot) — Open-source design and prototyping platform for collaborative design workflows. - [Connect Canva](https://claw-link.dev/openclaw/canva) — Create designs, upload assets, export content, and manage brand templates