How to connect Vercel to OpenClaw

The ClawHub skill teaches OpenClaw about Vercel, but the calls run through the ClawLink plugin and your connected account. Make sure Vercel 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.

Reconnect Vercel from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

Vercel 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 Vercel 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.

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.

Search results for "invalid token" on this provider answer about tokens you would actually see: an AI_GATEWAY_API_KEY in a deploy, a CRON_SECRET, a CLI token checked with whoami. None of those exist in a hosted connection, because the only token involved is the one you pasted at setup, held server-side. If every Vercel call fails with an invalid-token error, the stored key was regenerated or deleted in Vercel afterwards, and re-pasting the current token from the dashboard is the fix. If only some calls fail, the token is valid and the account simply lacks access to that team or project. What is not the cause is OpenClaw's gateway device token, which is what most "AUTH_TOKEN_MISMATCH" search answers actually discuss.

Ask the agent to diagnose it:

Call vercel_get_auth_user to check which Vercel account the connection acts as, then quote the exact error from the failed call. If it is an invalid-token error I will re-paste the key; do not retry before then.

Two usual causes, and both are about the request rather than the connection. First, the connected account may not hold the role the action needs: Vercel gates operations by team membership and role, so a member who can read deployments cannot necessarily add environment variables or transfer projects, and a team you are not part of returns a permission error rather than a not-found. Second, the agent may have sent a placeholder or guessed id (like "YOUR_ID" or a project name from documentation) instead of a real one: ask it to run vercel_get_projects first and retry with the real project id. Most 403s at this stage are one of these two, not a ClawLink bug.

Ask the agent to diagnose it:

Run vercel_get_projects and vercel_get_teams and show me the real ids. Quote the exact 403 text, then retry the failing action with a real id from that list.

Vercel rate-limits its API, and an agent walking a large team's deployments, one call per deployment, is exactly the traffic shape that meets the limit. The response is not to retry immediately but to change the shape of the work: ask for one project or one deployment rather than a full sweep, and have the agent tell you what it intends to enumerate before it starts. If a bulk audit is genuinely needed, running it in stages across a few turns is more reliable than one sweep, and reads like vercel_get_deployments exist precisely so the agent can page through results instead of fetching them one at a time.

Ask the agent to diagnose it:

Tell me how many Vercel calls you have made in the last minute and what you were enumerating. Quote any rate-limit text from the last response. Do not call Vercel again until I reply.

Two different failures. If OpenClaw shows no Vercel tools at all, the connection or pairing is incomplete: confirm the skill was installed, that Vercel shows as connected in the dashboard, and start a fresh chat so the tool catalog reloads. If most tools work and a single name fails, that name is wrong rather than missing, and Vercel's verb-last naming makes guesses likely (vercel_add_environment_variable, vercel_get_deployments): the error lists the closest real tools, and clawlink_list_tools --integration vercel shows the exact catalog. There is also a first-call timing case: schemas load on demand, so the opening Vercel call in a fresh session can arrive before the catalog and needs one retry.

Ask the agent to diagnose it:

List the Vercel tools you actually have access to. If there are none, run clawlink_list_integrations and say so plainly. If there are, tell me which one lists projects and use that exact name.

Double-check that the API key for Vercel has the right scopes or account access. A valid key can still be too limited for some reads or writes.

Yes. ClawLink is the fastest way to connect OpenClaw to Vercel: link your Vercel account once in the browser and OpenClaw can call the Vercel API through 131 ready-made tools — no custom code or token handling.

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Vercel skill from ClawHub, then you click Connect in the dashboard to authorize Vercel. OpenClaw calls the tools from the next message — no config files, and the Vercel key you paste is stored server-side instead of in your environment.

About two minutes. Sign in, click Connect next to Vercel in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

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 Vercel working from chat.

A Vercel API token, generated in your Vercel account settings, entered once on the hosted setup page. It carries your Vercel user's access, so the agent sees the teams, projects, and deployments that you see. Because it is stored server-side rather than in an environment file or a CLI config, it is not sitting on any machine you happen to have used, rotating it in Vercel means updating a single place, and disconnecting from the ClawLink dashboard revokes the agent's use of it immediately.

Vercel's OIDC tokens are the no-secret path for a deployment inside Vercel to authenticate to Vercel's own AI Gateway: Vercel issues the token, Vercel consumes it, and there is nothing to rotate. That mechanism is not available to an agent sitting outside Vercel that wants to manage your projects, which is what this connection does. Hosted OAuth is the same idea for that job: the credential exists only server-side, the agent never sees it, and the connection is the single place it is granted and revoked. The two stories answer the same "no keys on my machine" worry from opposite ends, and this page is the agent-side one.

The 131 tools cover the project surface: projects and their settings, deployments and their logs and file contents, environment variables, domains and their DNS records, teams and members. The writes to be deliberate about are creating deployments, adding environment variables, and changing domains, because those are live: a deployment can ship, an environment variable can break a build, and a domain change re-points traffic. Reads, starting with vercel_get_projects and vercel_get_deployments, are the safe first steps.

The alternative routes that search results teach are about standing up infrastructure: the vercel-openclaw deployment template, the vclaw CLI, or an MCP server you configure and keep running, each with its own token handling. Here the skill install and one dashboard connection are the entire client-side story, and Vercel sits alongside your other connected accounts with one place to revoke. Choose on how much you want to run, not on features.

The ClawHub skill teaches OpenClaw about Vercel, but the calls run through the ClawLink plugin and your connected account. Make sure Vercel 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.