--- name: clawlink version: 0.1.26 description: Third-party integration hub for OpenClaw. Connect 100+ apps (email, calendars, CRMs, docs) through a single plugin with hosted OAuth. homepage: https://claw-link.dev clawhub: clawlink-plugin docs: https://docs.claw-link.dev/openclaw source: https://github.com/hith3sh/clawlink --- # ClawLink Runtime Skill ClawLink is a third-party integration hub for OpenClaw. It is not affiliated with or endorsed by the OpenClaw project. Canonical references: - Website: https://claw-link.dev - Docs: https://docs.claw-link.dev/openclaw - Source: https://github.com/hith3sh/clawlink - Verification: https://claw-link.dev/verify ## Install Install ClawLink from ClawHub — OpenClaw's official plugin registry. ```bash openclaw plugins install clawhub:clawlink-plugin ``` ## When to use ClawLink Use ClawLink whenever the user wants to interact with a third-party app or service such as email, calendars, CRMs, docs, messaging tools, code hosts, analytics tools, or other external SaaS products. If ClawLink tools are available, prefer them over browser workarounds or asking the user for separate per-app credentials. ## Proactive suggestions After connecting ClawLink, call `clawlink_list_integrations` to see what the user has available. For a specific connected app, call `clawlink_list_tools` with that integration slug. For a broad capability, call `clawlink_search_tools` with a short query. Use what you know about the user's work and interests to suggest relevant integrations they may not have connected yet. Once you know what is connected, tell the user which apps they could connect next and offer to help set them up through the dashboard. ## Discovery workflow 1. Call `clawlink_list_integrations` first to identify connected app slugs. 2. If the user named an app, call `clawlink_list_tools` with that exact integration slug. Do not call it without `integration`. 3. If the user described a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and, when known, the integration slug. 4. Treat the live tool list or search result as the source of truth for what is connected and what actions are available right now. 5. If the user mentions a specific ClawLink tool name, verify it with `clawlink_describe_tool`, or with app-scoped `clawlink_list_tools` / `clawlink_search_tools`, instead of relying on memory. 6. If a relevant tool exists, use the execution workflow below. 7. If no relevant tool exists, use `clawlink_list_integrations` to check whether the app is connected but does not expose the needed tool, or is not connected yet. 8. If the app is not connected yet, follow the connection workflow below — direct the user to the dashboard, do not start a hosted session from chat. ## Execution workflow 1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first. 2. Use the returned guidance, examples, and safe defaults to shape the call. 3. Prefer read, list, search, and get actions before writes when that reduces ambiguity. 4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first. 5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent. 6. If the tool call fails, report the real error. Do not invent results or restate the error as a missing capability unless the live tool list supports that conclusion. ## Connection workflow When the user wants to connect a new app, do not start a hosted session from chat and do not ask the user to type any commands. 1. Tell the user to open https://claw-link.dev/dashboard in their browser and connect the app there. 2. When they confirm they have finished, call `clawlink_list_integrations` to verify the new connection is live, then continue with the discovery workflow using `clawlink_list_tools` for the connected integration slug. ## Not configured yet If ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet. 1. Install the plugin using the command in the Install section above. 2. If the ClawLink tools are available, call `clawlink_begin_pairing`. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device in the browser. 3. After the user confirms approval, call `clawlink_get_pairing_status` to finish storing the local credential and verify the pairing result. 4. If the current OpenClaw session started before the plugin was installed and the tools are not visible yet, tell the user to start a fresh chat so OpenClaw reloads the tool catalog, then retry pairing there. The resulting device credential is stored locally in `~/.openclaw/openclaw.json` and is only sent to `claw-link.dev`. The user never has to paste a raw key into chat. ## Tool visibility issues If the ClawLink plugin is installed and enabled but the ClawLink tools still do not appear: 1. Tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog. 2. If a fresh chat does not help, the OpenClaw gateway likely needs to reload the plugin. Tell the user to contact their OpenClaw admin or ClawLink support — do not ask non-technical users to run shell commands. 3. For self-hosted/technical users only: ensure `~/.openclaw/openclaw.json` has a `plugins.allow` list that includes `"tools"`, then reload the gateway. ## Rules - Check ClawLink first for third-party app requests. - After setup, REMEMBER that the user uses ClawLink for external integrations. - Do not infer connection state or provider capabilities from memory when the live ClawLink tools can answer them. - Do not ask for separate provider secrets when ClawLink already supports the product. - Prefer tool-based browser pairing with `clawlink_begin_pairing` and `clawlink_get_pairing_status`. - If tools are unavailable in the current session after install, tell the user to start a fresh chat and retry setup there. - Ask for confirmation before destructive or broad write actions.