Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.claw-link.dev/llms.txt

Use this file to discover all available pages before exploring further.

ClawLink works with OpenClaw through the @useclawlink/openclaw-plugin package. Install the plugin once, approve this device in your browser, then connect apps from the ClawLink dashboard.
1

Install the plugin

openclaw plugins install @useclawlink/openclaw-plugin
openclaw gateway restart
If the current chat started before the plugin was installed and the ClawLink tools do not appear yet, start a fresh chat so OpenClaw reloads the plugin catalog.
2

Start browser pairing

In OpenClaw, ask the assistant to set up ClawLink or start pairing. The plugin starts a pairing session and gives you a browser URL.
3

Approve this device in your browser

Open the pairing URL, sign in to ClawLink if needed, and click Approve this device.
4

Let OpenClaw finish the pairing check

Return to OpenClaw so the plugin can finish the local save step and confirm that the device is paired.
5

Connect apps from the dashboard

Open Dashboard > Connections, add the apps you want, and start using them from OpenClaw.

​
What pairing stores locally

Browser pairing creates a device credential in the same cllk_live_... format as manual API keys and stores it locally in ~/.openclaw/openclaw.json. In the recommended flow, you never have to paste that raw key into chat. OpenClaw stores it for the plugin after the browser approval finishes.

​
Available plugin tools

After setup, the plugin exposes tools for pairing, connection management, tool discovery, previews, and execution:
  • clawlink_begin_pairing
  • clawlink_get_pairing_status
  • clawlink_start_connection
  • clawlink_get_connection_status
  • clawlink_list_integrations
  • clawlink_list_tools
  • clawlink_describe_tool
  • clawlink_preview_tool
  • clawlink_call_tool

​
Manual fallback

Use Settings > API Keys only if your OpenClaw client exposes a plugin settings UI and browser pairing is not available. In that fallback path:
  1. Create a key in Settings > API Keys
  2. Copy the raw cllk_live_... value when it is shown
  3. Paste it into the plugin settings field
Most users should skip this and use browser pairing instead.