# How to connect Motion to OpenClaw (paste one key, 27 tools) > Connect Motion to OpenClaw with ClawLink: paste your Motion key once and 27 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/motion The usual route to Motion 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 Motion setup: install one ClawHub skill, connect Motion in the browser, and OpenClaw can call real Motion actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/motion ## Setup It takes three steps to connect OpenClaw to Motion. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Motion** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **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 motion # connect Motion (browser OAuth) npx -y @useclawlink/cli actions motion # list available actions npx -y @useclawlink/cli run motion --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 Motion in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Motion API key once. Verify the connection by asking OpenClaw: > Create it in Motion 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Motion is connected in the dashboard, that agent calls the same 27 Motion 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). ## Motion MCP for OpenClaw Looking for a Motion MCP server for OpenClaw? ClawLink connects Motion to OpenClaw and exposes 27 Motion 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 Motion integration](https://claw-link.dev/hermes/motion) works the same way. ## What the OpenClaw Motion integration can do 27 Motion tools are ready for OpenClaw once the account is connected. The 22 below are the ones people reach for most; your agent can call all 27. ### 22 of 27 Motion tools for OpenClaw | Tool | What it does | |---|---| | **Create comment** `motion_create_comment` | Create a comment on a Motion task | | **Create project** `motion_create_project` | Create a new Motion project | | **Create task** `motion_create_task` | Create a new Motion task | | **Get my user** `motion_get_my_user` | Get the connected Motion user | | **Get project** `motion_get_project` | Get a Motion project by ID | | **Get task** `motion_get_task` | Get a Motion task by ID | | **List comments** `motion_list_comments` | List Motion comments | | **List projects** `motion_list_projects` | List Motion projects | | **List recurring tasks** `motion_list_recurring_tasks` | List Motion recurring tasks | | **List schedules** `motion_list_schedules` | List Motion schedules | | **List tasks** `motion_list_tasks` | List Motion tasks | | **List users** `motion_list_users` | List Motion workspace users | | **List workspaces** `motion_list_workspaces` | List Motion workspaces | | **Move task** `motion_move_task` | Move a Motion task to another project or status | | **Update task** `motion_update_task` | Update a Motion task | | **List custom fields** `motion_list_custom_fields` | Retrieve all custom fields for a given Motion workspace | | **List statuses** `motion_list_statuses` | Get a list of statuses for a Motion workspace | | **Add custom field to project** `motion_add_custom_field_to_project` | Add a custom field value to a project in Motion | | **Add custom field to task** `motion_add_custom_field_to_task` | Add a custom field value to a task in Motion | | **Create custom field** `motion_create_custom_field` | Create a new custom field in a Motion workspace | | **Create recurring task** `motion_create_recurring_task` | Create a new recurring task in Motion | | **Unassign task** `motion_unassign_task` | Unassign a task from its current assignee | ## Example prompts **Create Comment** > Create it in Motion for me, then confirm the important fields before you finish. **Create Project** > Create it in Motion for me, then confirm the important fields before you finish. **Create Task** > Create it in Motion for me, then confirm the important fields before you finish. **Get My User** > Pull the relevant data from Motion, 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 Motion working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Motion API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Motion 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 Motion. | 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 Motion actions to the runtime in a format your agent can reliably use. | 27 tools for Motion are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Motion 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 Motion in the browser, and the 27 tools above work from chat. There is no SDK and no config file, and the Motion 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 Motion skill but can't call the tools The ClawHub skill teaches OpenClaw about Motion, but the calls run through the ClawLink plugin and your connected account. Make sure Motion 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 Motion 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 Motion tools Motion 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 Motion 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. ### Motion 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 Motion has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Motion integration? Yes. ClawLink is the fastest way to connect OpenClaw to Motion: link your Motion account once in the browser and OpenClaw can call the Motion API through 27 ready-made tools — no custom code or token handling. ### How do I add Motion to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Motion skill from ClawHub, then you click Connect in the dashboard to authorize Motion. OpenClaw calls the tools from the next message — no config files, and the Motion key you paste is stored server-side instead of in your environment. ### How long does it take to connect Motion to OpenClaw? About two minutes. Sign in, click Connect next to Motion in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Motion 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 Motion working from chat. ### OpenClaw installed the Motion skill but can't call the tools The ClawHub skill teaches OpenClaw about Motion, but the calls run through the ClawLink plugin and your connected account. Make sure Motion 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 - [DocuSign](https://claw-link.dev/openclaw/docusign) — Send, sign, and manage agreements and envelopes - [Trello](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [Moco](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions.