# How to connect Edworking to OpenClaw (paste one key, 12 tools) > Connect Edworking to OpenClaw with ClawLink: paste your Edworking 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/edworking The usual route to Edworking 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 Edworking setup: install one ClawHub skill, connect Edworking in the browser, and OpenClaw can call real Edworking 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 Edworking. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Edworking** — 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 edworking # connect Edworking (browser OAuth) npx -y @useclawlink/cli actions edworking # list available actions npx -y @useclawlink/cli run edworking --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 Edworking in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Edworking API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Edworking, 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 Edworking is connected in the dashboard, that agent calls the same 12 Edworking 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). ## Edworking MCP for OpenClaw Looking for a Edworking MCP server for OpenClaw? ClawLink connects Edworking to OpenClaw and exposes 12 Edworking 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 Edworking integration](https://claw-link.dev/hermes/edworking) works the same way. ## What the OpenClaw Edworking integration can do 12 Edworking tools are ready for OpenClaw once the account is connected. The 11 below are the ones people reach for most; your agent can call all 12. ### 11 of 12 Edworking tools for OpenClaw | Tool | What it does | |---|---| | **Get task** `edworking_get_task` | Get one task with its project, state, assignees, and time entries | | **List folders** `edworking_list_folders` | List folders in an Edworking project, optionally restricted to children of a parent folder | | **List messages** `edworking_list_messages` | List Edworking's message/activity records for one project from a zero-based offset | | **List projects** `edworking_list_projects` | List the Edworking projects available to the connected account, returning IDs needed by | | **List states** `edworking_list_states` | List the workflow states configured for an Edworking project for inspection | | **List tasks** `edworking_list_tasks` | List tasks, optionally within one Edworking project, with concise status and tracking | | **Add time entry** `edworking_add_time_entry` | Record a duration against a task at a specified start time | | **Create task** `edworking_create_task` | Create a named task in an Edworking project | | **Update task** `edworking_update_task` | Update an existing task's name within its Edworking project | | **Remove time entry** `edworking_remove_time_entry` | Permanently remove one tracked-time entry by ID | | **Send message** `edworking_send_message` | Irreversibly send a text message to an Edworking project | ## Example prompts **Get Task** > Pull the relevant data from Edworking, summarize it in plain English, and point out anything that needs attention. **List Folders** > List the relevant items in Edworking, group them by priority, and recommend what OpenClaw should do next. **List Messages** > List the relevant items in Edworking, group them by priority, and recommend what OpenClaw should do next. **List Projects** > List the relevant items in Edworking, 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 Edworking working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Edworking API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Edworking 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 Edworking. | 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 Edworking actions to the runtime in a format your agent can reliably use. | 12 tools for Edworking are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Edworking 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 Edworking in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Edworking 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 Edworking skill but can't call the tools The ClawHub skill teaches OpenClaw about Edworking, but the calls run through the ClawLink plugin and your connected account. Make sure Edworking 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 Edworking 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 Edworking tools Edworking 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 Edworking 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. ### Edworking 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 Edworking has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Edworking integration? Yes. ClawLink is the fastest way to connect OpenClaw to Edworking: link your Edworking account once in the browser and OpenClaw can call the Edworking API through 12 ready-made tools — no custom code or token handling. ### How do I add Edworking to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Edworking skill from ClawHub, then you click Connect in the dashboard to authorize Edworking. OpenClaw calls the tools from the next message — no config files, and the Edworking key you paste is stored server-side instead of in your environment. ### How long does it take to connect Edworking to OpenClaw? About two minutes. Sign in, click Connect next to Edworking in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Edworking 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 Edworking working from chat. ### OpenClaw installed the Edworking skill but can't call the tools The ClawHub skill teaches OpenClaw about Edworking, but the calls run through the ClawLink plugin and your connected account. Make sure Edworking 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 - [Trello tools](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. - [ClickUp](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints