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.

Start every debugging session with Request Logs. Go to your dashboard and open the logs to see exactly which integration was called, what action was attempted, and any error message returned. Most issues can be diagnosed in under a minute from the logs alone.

​
Common issues

A Needs reconnect status usually means the provider credentials expired, were revoked, or need fresh consent.To fix this:
1

Go to Dashboard > Connections

Open your dashboard and navigate to Connections.
2

Expand the affected row

Find the affected app and expand its connection row.
3

Run the hosted reconnect flow

Click Reconnect and finish the provider flow in the popup.
If your agent is making requests but they’re failing, check the Request Logs for details.To diagnose this:
  1. Go to your dashboard and open Request Logs
  2. Find the failed request—the log shows the integration, the action attempted, and the error message returned
  3. Use the error message to identify whether the issue is with your credentials, the request itself, or the third-party service
Common causes include invalid parameters, permissions issues with the connected account, or the third-party service being temporarily unavailable.
Rate limit errors mean the third-party API (not ClawLink) has throttled requests from your account. This happens when too many calls are made in a short window.ClawLink automatically retries rate-limited requests with exponential backoff—so occasional rate limits resolve themselves. If failures persist, your agent is making requests faster than the third-party API allows.To resolve persistent rate limiting:
  • Slow down how frequently your agent triggers the affected integration
  • Check the third-party service’s rate limit documentation to understand the limits for your account tier
  • Consider upgrading your account with the third-party service if you need higher throughput
Some integrations—including Gmail, Google Sheets, and Google Calendar—use OAuth tokens that expire over time. When a token expires, the integration will stop working until you refresh it.To fix this:
1

Go to Dashboard > Connections

Open your dashboard and navigate to Connections.
2

Reconnect to get a fresh token

Expand the affected row and click Reconnect. This runs the hosted provider flow again and refreshes the token.
Manual key entry is a fallback path. If it fails, the simplest fix is usually to switch back to browser pairing.Check the following:
  • Make sure the key starts with cllk_live_...
  • Confirm you copied the raw key when it was first shown after creation
  • Revoke old keys you no longer trust and create a fresh one if needed
  • If possible, remove the manual key and run browser pairing instead
If your agent is running but you don’t see requests in the logs, try the following:
  1. Refresh the logs page—there can be a short delay before new entries appear
  2. Confirm the device is paired—if OpenClaw is not authenticated to ClawLink, requests never reach tool execution
  3. Verify the app is actually connected—an unconnected provider cannot produce tool execution rows
  4. Check the local credential—if the device credential was revoked, requests are rejected before they are logged
If requests still do not appear after a few minutes, run pairing again and make sure the app is connected in Connections.