# How to connect Connecteam to OpenClaw (paste one key, 16 tools) > Connect Connecteam to OpenClaw with ClawLink: paste your Connecteam key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/connecteam The usual route to Connecteam 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 Connecteam setup: install one ClawHub skill, connect Connecteam in the browser, and OpenClaw can call real Connecteam 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 Connecteam. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Connecteam** — 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 connecteam # connect Connecteam (browser OAuth) npx -y @useclawlink/cli actions connecteam # list available actions npx -y @useclawlink/cli run connecteam --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 Connecteam in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Connecteam API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Connecteam, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Connecteam is connected in the dashboard, that agent calls the same 16 Connecteam 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). ## Connecteam MCP for OpenClaw Looking for a Connecteam MCP server for OpenClaw? ClawLink connects Connecteam to OpenClaw and exposes 16 Connecteam 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 Connecteam integration](https://claw-link.dev/hermes/connecteam) works the same way. ## What the OpenClaw Connecteam integration can do 16 Connecteam tools are ready for OpenClaw once the account is connected. ### All 16 Connecteam tools for OpenClaw | Tool | What it does | |---|---| | **Get chat** `connecteam_get_chat` | Retrieve chat conversations | | **Get custom field categories** `connecteam_get_custom_field_categories` | Retrieve all custom field categories | | **Get custom fields** `connecteam_get_custom_fields` | Retrieve all custom fields associated with the account | | **Get forms** `connecteam_get_forms` | Retrieve all form definitions from Connecteam | | **Get jobs** `connecteam_get_jobs` | Retrieve a list of job objects relevant to a specific instance ID | | **Get performance indicators** `connecteam_get_performance_indicators` | Retrieve the list of performance metric indicators | | **Get policy types** `connecteam_get_policy_types` | Retrieve available time-off policy types | | **Get publishers** `connecteam_get_publishers` | Retrieve a list of all custom publishers | | **Get schedulers** `connecteam_get_schedulers` | Retrieve a list of job schedulers associated with the account | | **Get smart groups** `connecteam_get_smart_groups` | Retrieve all smart groups associated with the account | | **Get task boards** `connecteam_get_task_boards` | Retrieve all task boards | | **Get users** `connecteam_get_users` | Retrieve a list of all users associated with your account | | **List me** `connecteam_list_me` | Retrieve account information including company name and company ID | | **Create users** `connecteam_create_users` | Create multiple users in Connecteam | | **Generate upload URL** `connecteam_generate_upload_url` | Generate a pre-signed URL for uploading a file | | **Archive users** `connecteam_archive_users` | Archive one or more users by their unique IDs | ## Example prompts **Get Chat** > Pull the relevant data from Connecteam, summarize it in plain English, and point out anything that needs attention. **Get Custom Field Categories** > Pull the relevant data from Connecteam, summarize it in plain English, and point out anything that needs attention. **Get Custom Fields** > Pull the relevant data from Connecteam, summarize it in plain English, and point out anything that needs attention. **Get Forms** > Pull the relevant data from Connecteam, 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 Connecteam working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Connecteam API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Connecteam 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 Connecteam. | 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 Connecteam actions to the runtime in a format your agent can reliably use. | 16 tools for Connecteam are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Connecteam 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 Connecteam in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the Connecteam 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 Connecteam skill but can't call the tools The ClawHub skill teaches OpenClaw about Connecteam, but the calls run through the ClawLink plugin and your connected account. Make sure Connecteam 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 Connecteam 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 Connecteam tools Connecteam 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 Connecteam 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. ### Connecteam 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 Connecteam has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Connecteam integration? Yes. ClawLink is the fastest way to connect OpenClaw to Connecteam: link your Connecteam account once in the browser and OpenClaw can call the Connecteam API through 16 ready-made tools — no custom code or token handling. ### How do I add Connecteam to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Connecteam skill from ClawHub, then you click Connect in the dashboard to authorize Connecteam. OpenClaw calls the tools from the next message — no config files, and the Connecteam key you paste is stored server-side instead of in your environment. ### How long does it take to connect Connecteam to OpenClaw? About two minutes. Sign in, click Connect next to Connecteam in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Connecteam 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 Connecteam working from chat. ### OpenClaw installed the Connecteam skill but can't call the tools The ClawHub skill teaches OpenClaw about Connecteam, but the calls run through the ClawLink plugin and your connected account. Make sure Connecteam 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 - [OpenClaw Greenhouse integration](https://claw-link.dev/openclaw/greenhouse) — Manage jobs, candidates, applications, and interviews - [OpenClaw Ashby integration](https://claw-link.dev/openclaw/ashby) — Ashby delivers an applicant tracking system for modern teams, offering features like job postings, candidate management, and data-driven hiring insights to streamline the recruitment process. - [Lever tools](https://claw-link.dev/openclaw/lever) — Manage candidates, opportunities, interviews, and requisitions