How to connect Heights Platform to OpenClaw
Connect Heights Platform to OpenClaw with ClawLink: paste your Heights Platform key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine.
Heights PlatformAPI KEYMCPHeights Platform helps creators build and sell online courses, digital products, and communities while managing students, orders, and access.. Once connected, OpenClaw can read and act on Heights Platform from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Heights Platform 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 Heights Platform setup: install one ClawHub skill, connect Heights Platform in the browser, and OpenClaw can call real Heights Platform 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 Heights Platform.
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 Heights Platform
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Heights Platform?"
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 Heights Platform in the ClawLink dashboard — paste your Heights Platform API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Heights Platform, 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 Heights Platform is connected in the dashboard, that agent calls the same 16 Heights Platform tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Heights Platform MCP for OpenClaw
Looking for a Heights Platform MCP server for OpenClaw? ClawLink connects Heights Platform to OpenClaw and exposes 16 Heights Platform tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Heights Platform integration works the same way.
What the OpenClaw Heights Platform integration can do
16 Heights Platform tools are ready for OpenClaw once the account is connected.
All 16 Heights Platform tools for OpenClaw
| Tool | What it does |
|---|---|
Get learning product heights_platform_get_learning_product | Get detailed metadata for one course, bundle, or digital product by ID |
Get order heights_platform_get_order | Get one Heights order by its public unique order ID |
Get student course progress heights_platform_get_student_course_progress | Get a student's overall and course-specific completion percentages for one course |
Get student details heights_platform_get_student_details | Get a student by email, including account attributes, activity counts, paid orders, and |
List course roles heights_platform_list_course_roles | List the Heights roles that can be granted to students |
List learning products heights_platform_list_learning_products | List published courses, bundles, or digital products in the connected Heights account |
List orders heights_platform_list_orders | List Heights orders with optional status, student email, and creation-time filters, returning |
List student submissions heights_platform_list_student_submissions | List assignment answers or project posts submitted by students |
List students heights_platform_list_students | List all Heights students one page at a time, or list the unpaginated students whose total |
Enroll student heights_platform_enroll_student | Create a student or update an existing student and mark them enrolled without granting course |
Grant student access heights_platform_grant_student_access | Grant one course or bundle to a student by creating a zero-dollar paid order |
Grant student role heights_platform_grant_student_role | Grant one Heights role to a student, changing the student's authorization |
Revoke student role heights_platform_revoke_student_role | Revoke one Heights role from a student, changing the student's authorization |
Unenroll student heights_platform_unenroll_student | End a student's paid membership by setting their Heights paying-student state to false |
Reset student progress heights_platform_reset_student_progress | Permanently erase a student's saved completion and progress records |
Revoke student access heights_platform_revoke_student_access | Permanently remove one course or bundle from a student's existing orders |
Try it: find the Heights Platform tool you need
Browse the 16 Heights Platform 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 Heights Platform, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Heights Platform, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Heights Platform, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Heights Platform, 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 Heights Platform working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Heights Platform API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Heights Platform 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 Heights Platform. | 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 Heights Platform actions to the runtime in a format your agent can reliably use. | 16 tools for Heights Platform are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Heights Platform 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 Heights Platform in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the Heights Platform 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 Heights Platform skill but can't call the tools
The ClawHub skill teaches OpenClaw about Heights Platform, but the calls run through the ClawLink plugin and your connected account. Make sure Heights Platform 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 Heights Platform 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 Heights Platform tools
Heights Platform 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 Heights Platform 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.
Heights Platform 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 Heights Platform 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 Heights Platform integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Heights Platform: link your Heights Platform account once in the browser and OpenClaw can call the Heights Platform API through 16 ready-made tools — no custom code or token handling.
How do I add Heights Platform to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Heights Platform skill from ClawHub, then you click Connect in the dashboard to authorize Heights Platform. OpenClaw calls the tools from the next message — no config files, and the Heights Platform key you paste is stored server-side instead of in your environment.
How long does it take to connect Heights Platform to OpenClaw?
About two minutes. Sign in, click Connect next to Heights Platform in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Heights Platform 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 Heights Platform working from chat.
OpenClaw installed the Heights Platform skill but can't call the tools
The ClawHub skill teaches OpenClaw about Heights Platform, but the calls run through the ClawLink plugin and your connected account. Make sure Heights Platform 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
Connect PagerDuty
Manage incidents, on-call schedules, and services
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.