Troubleshooting

Fix common issues with ClawLink integrations and agent connectivity

Start every debugging session in Dashboard > Logs. Open the failed call to see the app, the action, the input your agent sent and the error the app returned. Most problems are clear from that one screen.

Start here

Find the bucket your problem is in first:

Common fixes

Connection shows "Needs reconnect"

The provider credential expired, was revoked, or needs new consent. Go to Connections, open the connection and click Reconnect. Then ask your agent to try the same task again.

Google apps (Gmail, Sheets, Calendar) and other OAuth apps can stop working this way when a token expires. Reconnecting runs the sign-in again and gets a new token.

The usual cause is a chat that started before the install, or an agent that has not reloaded the plugin.

  • Start a new chat after you install the plugin, so the agent loads the new tools.
  • Restart the agent. For OpenClaw: openclaw gateway restart.
  • Make sure the device shows in Dashboard > Devices, and your apps show Connected in Connections.
  • Still missing? Pair the device again: see Install ClawLink.

Tool calls are failing

Open the failed call in Logs. It shows which app ran, which action, the input your agent sent, and the error.

Common causes:

  • A placeholder value. The agent sent YOUR_ID or example.com instead of a real id. Ask it to look the id up first.
  • A missing permission. The connected account cannot do this action. Reconnect with an account that can.
  • An expired sign-in. The connection needs a reconnect.
  • A short provider outage. Try again in a few minutes.

Pairing links are short-lived. If the browser page says the session expired, or your agent never finishes after you approve, start again:

Start pairing again

Ask your agent to set up ClawLink, or run npx -y @useclawlink/cli login again.

Approve the new link

Open the new link, sign in if necessary, and click Approve this device.

Go back to your agent

The agent finishes the local save step and confirms that it is paired.

Rate limit or quota errors

  • Rate limited: the app limits how fast you can call it. ClawLink retries short bursts, but a loop that calls too often still fails. Slow the workflow down.
  • Monthly limit reached: you used all your tool calls for this period. See your usage in Dashboard > Billing, or move to Ultra Heavy.
  • Out of data credit: a public data app call needs credit. Top up in Dashboard > Billing.

Manual API key setup does not work

A manual key is a fallback. Browser pairing is usually the simplest fix.

  • Make sure the key starts with cllk_live_.
  • Make sure you copied the full raw key when it first showed.
  • Revoke old keys you no longer trust, and create a new one in Settings > Developer.

Still stuck?

Open the support chat in the dashboard. A real person replies, usually within minutes. Include the time of the failed call, or its details from Logs.

On this page