How to connect Shortcut to OpenClaw
Connect Shortcut to OpenClaw with ClawLink: paste your Shortcut key once and 136 tools work from chat. No MCP server to run, nothing stored on your machine.
ShortcutAPI KEYMCPShortcut aligns product development work with company objectives so teams can execute with a shared purpose.. Once connected, OpenClaw can read and act on Shortcut from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Shortcut 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 Shortcut setup: install one ClawHub skill, connect Shortcut in the browser, and OpenClaw can call real Shortcut actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Shortcut 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 "Shortcut" (hith3sh/shortcut-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/shortcut-workspace
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 Shortcut.
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 Shortcut
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Shortcut?"
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 Shortcut in the ClawLink dashboard — paste your Shortcut API key once.
Verify the connection by asking OpenClaw:
Create it in Shortcut for me, then confirm the important fields before you finish.
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 Shortcut is connected in the dashboard, that agent calls the same 136 Shortcut tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Shortcut MCP for OpenClaw
Looking for a Shortcut MCP server for OpenClaw? ClawLink connects Shortcut to OpenClaw and exposes 136 Shortcut tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Shortcut integration works the same way.
What the OpenClaw Shortcut integration can do
136 Shortcut tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 136.
30 of 136 Shortcut tools for OpenClaw
| Tool | What it does |
|---|---|
Create category shortcut_create_category | Create Category allows you to create a new Category in Shortcut. |
Create doc shortcut_create_doc | Create Doc allows you to create a new document in Shortcut |
Create entity template shortcut_create_entity_template | Create a new entity template for the Workspace. |
Create epic shortcut_create_epic | Create Epic allows you to create a new Epic in Shortcut. |
Get category shortcut_get_category | Get Category returns information about the selected Category. |
Get current member info shortcut_get_current_member_info | Returns information about the authenticated member. |
Get custom field shortcut_get_custom_field | Retrieves detailed information about a specific custom field in Shortcut using its unique public identifier |
Get doc shortcut_get_doc | Get Doc returns information about a chosen Doc by its public ID |
Get entity template shortcut_get_entity_template | Get Entity Template returns information about a given entity template. |
Get epic shortcut_get_epic | Get Epic returns information about the selected Epic. |
Get epic comment shortcut_get_epic_comment | This endpoint returns information about the selected Epic Comment. |
Get epic health shortcut_get_epic_health | Get the current health status for the specified Epic |
Get epic workflow shortcut_get_epic_workflow | Returns the Epic Workflow for the Workspace |
Get external link stories shortcut_get_external_link_stories | Get Stories which have a given External Link associated with them |
Get file shortcut_get_file | Get File returns information about the selected UploadedFile |
Get generic integration shortcut_get_generic_integration | Get Generic Integration returns information about a webhook integration by its ID |
Get group shortcut_get_group | Retrieves detailed information about a specific group in the Shortcut workspace using its |
Get iteration shortcut_get_iteration | Retrieves detailed information about a specific iteration in the Shortcut project management |
Get key result shortcut_get_key_result | Get Key Result returns information about a chosen Key Result |
Get label shortcut_get_label | Get Label returns information about the selected Label |
Get linked file shortcut_get_linked_file | Get File returns information about the selected Linked File |
Get member shortcut_get_member | Returns information about a Member |
Get objective shortcut_get_objective | Get Objective returns information about a chosen Objective |
Get project shortcut_get_project | Get Project returns information about the selected Project |
Get repository shortcut_get_repository | Get Repository returns information about the selected Repository |
Get story shortcut_get_story | Get Story returns information about a chosen Story |
Get story comment shortcut_get_story_comment | Get Comment is used to get Comment information |
Get story link shortcut_get_story_link | Returns the stories and their relationship for the given Story Link |
Get task shortcut_get_task | Returns information about a chosen Task |
Get workflow shortcut_get_workflow | Get Workflow returns information about a chosen Workflow |
Try it: find the Shortcut tool you need
Browse the 30 Shortcut tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Create it in Shortcut for me, then confirm the important fields before you finish.
Create it in Shortcut for me, then confirm the important fields before you finish.
Create it in Shortcut for me, then confirm the important fields before you finish.
Create it in Shortcut for me, then confirm the important fields before you finish.
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 Shortcut working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Shortcut API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Shortcut 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 Shortcut. | 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 Shortcut actions to the runtime in a format your agent can reliably use. | 136 tools for Shortcut are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Shortcut 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 Shortcut in the browser, and the 136 tools above work from chat. There is no SDK and no config file, and the Shortcut 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 Shortcut skill but can't call the tools
The ClawHub skill teaches OpenClaw about Shortcut, but the calls run through the ClawLink plugin and your connected account. Make sure Shortcut 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 Shortcut 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 Shortcut tools
Shortcut 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 Shortcut 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.
Shortcut 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 Shortcut 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 Shortcut integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Shortcut: link your Shortcut account once in the browser and OpenClaw can call the Shortcut API through 136 ready-made tools — no custom code or token handling.
How do I add Shortcut to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Shortcut skill from ClawHub, then you click Connect in the dashboard to authorize Shortcut. OpenClaw calls the tools from the next message — no config files, and the Shortcut key you paste is stored server-side instead of in your environment.
How long does it take to connect Shortcut to OpenClaw?
About two minutes. Sign in, click Connect next to Shortcut in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Shortcut 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 Shortcut working from chat.
OpenClaw installed the Shortcut skill but can't call the tools
The ClawHub skill teaches OpenClaw about Shortcut, but the calls run through the ClawLink plugin and your connected account. Make sure Shortcut 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.
