How to connect Hyperise to OpenClaw
Connect Hyperise to OpenClaw with ClawLink: paste your Hyperise key once and 5 tools work from chat. No MCP server to run, nothing stored on your machine.
HyperiseAPI KEYMCPHyperise is a personalization toolkit that enables sales and marketing teams to add dynamic, personalized elements to images, videos, and websites, enhancing engagement across various channels.. Once connected, OpenClaw can read and act on Hyperise from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Hyperise 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 Hyperise setup: install one ClawHub skill, connect Hyperise in the browser, and OpenClaw can call real Hyperise 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 Hyperise.
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 Hyperise
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Hyperise?"
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 Hyperise in the ClawLink dashboard — paste your Hyperise API key once.
Verify the connection by asking OpenClaw:
List the relevant items in Hyperise, group them by priority, and recommend what OpenClaw should do next.
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 Hyperise is connected in the dashboard, that agent calls the same 5 Hyperise tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Hyperise MCP for OpenClaw
Looking for a Hyperise MCP server for OpenClaw? ClawLink connects Hyperise to OpenClaw and exposes 5 Hyperise tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Hyperise integration works the same way.
What the OpenClaw Hyperise integration can do
5 Hyperise tools are ready for OpenClaw once the account is connected.
All 5 Hyperise tools for OpenClaw
| Tool | What it does |
|---|---|
List image templates hyperise_list_image_templates | Retrieves all active personalized image templates for the authenticated user |
User authentication hyperise_user_authentication | Authenticate an API token and retrieve user details |
Create client account hyperise_create_client_account | Creates a new Hyperise business/client account for personalized image campaigns |
Personalized short links hyperise_personalized_short_links | Generate a personalized short link with Open Graph metadata for rich link previews |
Prospect business data hyperise_prospect_business_data | Perform CRUD operations on Hyperise business prospect records |
Try it: find the Hyperise tool you need
Browse the 5 Hyperise tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
List the relevant items in Hyperise, group them by priority, and recommend what OpenClaw should do next.
Use Hyperise to user authentication and walk me through the result in plain English.
Create it in Hyperise for me, then confirm the important fields before you finish.
Use Hyperise to personalized short links and walk me through the result in plain English.
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 Hyperise working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Hyperise API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Hyperise 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 Hyperise. | 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 Hyperise actions to the runtime in a format your agent can reliably use. | 5 tools for Hyperise are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Hyperise 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 Hyperise in the browser, and the 5 tools above work from chat. There is no SDK and no config file, and the Hyperise 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 Hyperise skill but can't call the tools
The ClawHub skill teaches OpenClaw about Hyperise, but the calls run through the ClawLink plugin and your connected account. Make sure Hyperise 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 Hyperise 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 Hyperise tools
Hyperise 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 Hyperise 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.
Hyperise 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 Hyperise 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 Hyperise integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Hyperise: link your Hyperise account once in the browser and OpenClaw can call the Hyperise API through 5 ready-made tools — no custom code or token handling.
How do I add Hyperise to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Hyperise skill from ClawHub, then you click Connect in the dashboard to authorize Hyperise. OpenClaw calls the tools from the next message — no config files, and the Hyperise key you paste is stored server-side instead of in your environment.
How long does it take to connect Hyperise to OpenClaw?
About two minutes. Sign in, click Connect next to Hyperise in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Hyperise 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 Hyperise working from chat.
OpenClaw installed the Hyperise skill but can't call the tools
The ClawHub skill teaches OpenClaw about Hyperise, but the calls run through the ClawLink plugin and your connected account. Make sure Hyperise 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
DataRobot
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
OpenClaw Chatbotkit integration
ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
OpenClaw Just One API integration
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.