# How to connect Teamwork to OpenClaw (paste one key, 12 tools) > Connect Teamwork to OpenClaw with ClawLink: paste your Teamwork key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/teamwork The usual route to Teamwork 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 Teamwork setup: install one ClawHub skill, connect Teamwork in the browser, and OpenClaw can call real Teamwork 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 Teamwork. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Teamwork** — 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 teamwork # connect Teamwork (browser OAuth) npx -y @useclawlink/cli actions teamwork # list available actions npx -y @useclawlink/cli run teamwork --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 Teamwork in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Teamwork API key once. Verify the connection by asking OpenClaw: > List the relevant items in Teamwork, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Teamwork is connected in the dashboard, that agent calls the same 12 Teamwork 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). ## Teamwork MCP for OpenClaw Looking for a Teamwork MCP server for OpenClaw? ClawLink connects Teamwork to OpenClaw and exposes 12 Teamwork 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 Teamwork integration](https://claw-link.dev/hermes/teamwork) works the same way. ## What the OpenClaw Teamwork integration can do 12 Teamwork tools are ready for OpenClaw once the account is connected. ### All 12 Teamwork tools for OpenClaw | Tool | What it does | |---|---| | **List milestones** `teamwork_list_milestones` | List visible Teamwork milestones by project, status, due-date range, assignee, or text | | **List people** `teamwork_list_people` | List people visible to the connected Teamwork user for assignment and ownership workflows | | **List projects** `teamwork_list_projects` | List projects visible to the connected Teamwork user, with focused filters for name, status | | **List tags** `teamwork_list_tags` | List Teamwork tags visible to the connected user, optionally filtered by project, item type | | **List task lists** `teamwork_list_task_lists` | List Teamwork task lists, usually within one or more projects, so an agent can place or locate | | **List tasks** `teamwork_list_tasks` | List and filter Teamwork tasks by project, task list, assignee, dates, completion state, or tags | | **List time entries** `teamwork_list_time_entries` | List accessible Teamwork time entries by project, task, person, date range, billing state, or | | **Search resources** `teamwork_search_resources` | Search across Teamwork projects, tasks, task lists, milestones, people, companies, time | | **Create tag** `teamwork_create_tag` | Create a Teamwork tag, or return the existing installation tag when the same name already exists | | **Create task** `teamwork_create_task` | Create a task in a Teamwork task list with common scheduling, assignment, estimate, privacy | | **Log time entry** `teamwork_log_time_entry` | Log time against a Teamwork task with a date, duration, optional start time, description | | **Update task** `teamwork_update_task` | Update selected fields of an existing Teamwork task while leaving omitted task fields unchanged | ## Example prompts **List Milestones** > List the relevant items in Teamwork, group them by priority, and recommend what OpenClaw should do next. **List People** > List the relevant items in Teamwork, group them by priority, and recommend what OpenClaw should do next. **List Projects** > List the relevant items in Teamwork, group them by priority, and recommend what OpenClaw should do next. **List Tags** > List the relevant items in Teamwork, 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 Teamwork working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Teamwork API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Teamwork 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 Teamwork. | 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 Teamwork actions to the runtime in a format your agent can reliably use. | 12 tools for Teamwork are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Teamwork 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 Teamwork in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Teamwork 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 Teamwork skill but can't call the tools The ClawHub skill teaches OpenClaw about Teamwork, but the calls run through the ClawLink plugin and your connected account. Make sure Teamwork 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 Teamwork 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 Teamwork tools Teamwork 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 Teamwork 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. ### Teamwork 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 Teamwork has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Teamwork integration? Yes. ClawLink is the fastest way to connect OpenClaw to Teamwork: link your Teamwork account once in the browser and OpenClaw can call the Teamwork API through 12 ready-made tools — no custom code or token handling. ### How do I add Teamwork to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Teamwork skill from ClawHub, then you click Connect in the dashboard to authorize Teamwork. OpenClaw calls the tools from the next message — no config files, and the Teamwork key you paste is stored server-side instead of in your environment. ### How long does it take to connect Teamwork to OpenClaw? About two minutes. Sign in, click Connect next to Teamwork in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Teamwork 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 Teamwork working from chat. ### OpenClaw installed the Teamwork skill but can't call the tools The ClawHub skill teaches OpenClaw about Teamwork, but the calls run through the ClawLink plugin and your connected account. Make sure Teamwork 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 - [Connect Trello](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [OpenClaw Moco integration](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [OpenClaw ClickUp integration](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints