Vercel

!Vercel

Manage Vercel projects, deployments, domains, environment variables, and team resources from chat via the Vercel REST API.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure Vercel API access yourself.

Setup in 3 Steps

How It Works

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│  Vercel REST     │
│   (User Chat)   │     │   (OAuth)    │     │      API         │
└─────────────────┘     └──────────────┘     └──────────────────┘
         │                       │                       │
         │  1. Install Plugin    │                       │
         │  2. Pair Device       │                       │
         │  3. Connect Vercel    │                       │
         │                       │  4. Secure Token       │
         │                       │  5. Proxy Requests    │
         │                       │                       │
         ▼                       ▼                       ▼
   ┌──────────┐           ┌──────────┐           ┌──────────┐
   │  SKILL   │           │ Dashboard│           │  Vercel │
   │  File    │           │ Auth     │           │ Account │
   └──────────┘           └──────────┘           └──────────┘

Install

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for Vercel again."

Quick Start

# List projects
clawlink_call_tool --tool "vercel_list_projects" --params '{}'

# Get deployment details
clawlink_call_tool --tool "vercel_get_deployment" --params '{"deployment_id": "DEPLOYMENT_ID"}'

# List deployments
clawlink_call_tool --tool "vercel_list_deployments" --params '{"project_name": "my-project"}'

Authentication

All Vercel tool calls are authenticated automatically by ClawLink using the user's connected Vercel account token.

No API token is required in chat. ClawLink stores the token securely and injects it into every Vercel API request on the user's behalf.

Getting Connected

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with clawlink_begin_pairing if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=vercel and connect Vercel.
4. Call clawlink_list_integrations to verify the connection is active.

Connection Management

List Connections

clawlink_list_integrations

Response: Returns all connected integrations. Look for vercel in the list.

Verify Connection

clawlink_list_tools --integration vercel

Response: Returns the live tool catalog for Vercel.

Reconnect

If Vercel tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=vercel
2. After they confirm, call clawlink_list_integrations to verify
3. Then call clawlink_list_tools --integration vercel

Security & Permissions

• Access is scoped to the Vercel account connected during OAuth setup and the scopes granted.
• All write operations (deploy, create project, update settings, add domains) require explicit user confirmation.
• Destructive operations (delete deployment, remove domain) are high-impact and must be confirmed.
• Environment variable changes can affect running deployments — confirm before modifying.

Tool Reference

Projects

Deployments

Domains

Environment Variables

Teams & Members

Secrets

Logs & Events

Code Examples

List all projects

clawlink_call_tool --tool "vercel_list_projects" \
  --params '{
    "team_id": "team_id"
  }'

Get deployment details

clawlink_call_tool --tool "vercel_get_deployment" \
  --params '{
    "deployment_id": "dpl_1234567890"
  }'

List deployments for a project

clawlink_call_tool --tool "vercel_list_deployments" \
  --params '{
    "project_name": "my-nextjs-app",
    "limit": 10
  }'

Add an environment variable

clawlink_call_tool --tool "vercel_add_env" \
  --params '{
    "project_name": "my-nextjs-app",
    "key": "DATABASE_URL",
    "value": "postgres://...",
    "environment": "production"
  }'

Verify a domain

clawlink_call_tool --tool "vercel_verify_domain" \
  --params '{
    "domain": "example.com"
  }'

Cancel a deployment

clawlink_call_tool --tool "vercel_cancel_deployment" \
  --params '{
    "deployment_id": "dpl_1234567890"
  }'

Discovery Workflow

1. Call clawlink_list_integrations to confirm Vercel is connected.
2. Call clawlink_list_tools --integration vercel to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration vercel.
5. If no Vercel tools appear, direct the user to https://claw-link.dev/dashboard?add=vercel.

Execution Workflow

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  list → get → describe                                      │
│                                                             │
│  Example: List projects → Get deployments → Show status     │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                    │
│  describe → preview → confirm → call                        │
│                                                             │
│  Example: Preview env var change → User approves → Update   │
└─────────────────────────────────────────────────────────────┘

1. For unfamiliar tools, ambiguous requests, or any write action, call clawlink_describe_tool first.
2. Use the returned guidance, schema, whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
3. Prefer read, list, and get operations 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 failure as a missing capability unless the live catalog supports that conclusion.

Notes

• Deployment IDs start with dpl_ and project names are used in deployment URLs.
• Environment variables can be scoped to development, preview, or production environments.
• Domain verification requires adding DNS records — check the verification status with vercel_get_domain.
• Deleted deployments cannot be restored.
• Team operations require the authenticated user to be a team owner or admin.
• Vercel uses a specific deployment URL format: https://project.vercel.app.

Error Handling

Troubleshooting: Tools Not Visible

1. Check that the ClawLink plugin is installed:

```bash

openclaw plugins list

```

1. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.
2. If a fresh chat does not help, run:

```bash

openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json

openclaw gateway restart

```

1. After restart, tell the user to send /new again and retry.

Resources

• Vercel REST API Documentation
• Vercel API Reference
• ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=vercel-deployments
• ClawLink Docs: https://docs.claw-link.dev/openclaw
• ClawLink Verification: https://claw-link.dev/verify

Powered by ClawLink — an integration hub for OpenClaw

!ClawLink Logo