Vercel deploys

Access

Vercel token, read deployments

Required. Env VERCEL_TOKEN. Mode api_key.

• Deployments: Read

In Vercel open Account Settings, then Tokens, and create a token named Botopticon board. Scope it to the team and projects you watch. The agent lists deployments and reads their status. It never creates, cancels, or promotes a deployment.

Botopticon never stores this key. Paste it into the agent, cron host, or MCP config. Revoke it any time.

Board

Sample · not your account.

Sample · not your account. The agent puts the ask on the board. You answer there. How Command Tiles work

• Redeploy www

  Needs you

  Sample data

  Approval · Vercel

  Redeploy www after the failed build?

  Production failed on the build step.

  ApproveReject

• Where should prod go?

  Needs you

  Sample data

  Question · Vercel

  The latest production deploy errored. What next?

  RedeployRoll backHold

Tiles

• Productionneeds you
• Recent deploys
• Failed 24h
• Current build

• Production. needs_you when the latest production deployment failed or errored.

Setup

1. 01

   Mint a read-only Vercel key

   Create a key that can only read. Never grant write. Keep it in the env var named on this page, on the agent or cron host. Botopticon never stores this key. Paste it into the agent, cron host, or MCP config. Revoke it any time.

2. 02

   Create a Botopticon token

   In the app, open Connection tokens and create one named after this board. Copy it. It is shown once. That token posts to Botopticon. It is not the source key.

3. 03

   Paste the prompt into your agent

   Open the tab for Grok Bot, Muse, MCP, Cursor, Claude, or curl. Replace $BOTOPTICON_TOKEN. The agent fetches the source, maps the fields in the brief, and posts. Do not paste canned sample JSON as live data.

4. 04

   Wait for the first live post

   These numbers are sample. They flip when your agent posts with the key. Each tile keeps the sample label until that tile is replaced.

Snippets

Same recipe, one tab per platform. Replace $BOTOPTICON_TOKEN with a connection token. The prompt fetches the source and posts. Do not paste the sample numbers as live data.

Paste this into Grok Bot. Replace $BOTOPTICON_TOKEN with a Botopticon connection token. Connect MCP at https://www.botopticon.com/api/mcp if this client can. If it cannot, POST /api/ingest with curl instead.

Keep the Botopticon board "Vercel deploys" current.

Source: Vercel.
You hold VERCEL_TOKEN (Vercel token, read deployments). Botopticon never stores this key. Paste it into the agent, cron host, or MCP config. Revoke it any time.
In Vercel open Account Settings, then Tokens, and create a token named Botopticon board. Scope it to the team and projects you watch. The agent lists deployments and reads their status. It never creates, cancels, or promotes a deployment.
Scopes (read-only): Deployments: Read.

What to fetch and how to map it:
Read the current Vercel REST docs. Objects: Deployment, DeploymentEvent.
Production: the latest deployment with target production (or the production alias). Status state needs_you when that deploy failed or errored. working while building. idle or done when READY.
Recent deploys: newest Deployments as a feed. Label project, target, and state.
Failed 24h: Deployments with error or failed state in the last 24 hours.
Current build: progress rows for the in-flight deployment's phases if Vercel reports them. If it only reports a single state, one row is enough. Do not invent percents.

Tiles:
- Production — bot Vercel, tile prod-now, type status. needs_you when the latest production deployment failed or errored. Sample shows needs_you true.
- Recent deploys — bot Vercel, tile deploy-feed, type feed.
- Failed 24h — bot Vercel, tile failed-24h, type kpi.
- Current build — bot Vercel, tile build-now, type progress.

Post each tile to https://www.botopticon.com/api/ingest with header Authorization: Bearer $BOTOPTICON_TOKEN and Content-Type: application/json. Fields: bot, tile, type, title, subtitle, props, needs_you, ttl_seconds.
If you can call MCP, connect to https://www.botopticon.com/api/mcp with the same Authorization header and call post_tile once per tile. The arguments are those JSON fields.
Do not invent numbers. Do not post the same body again just to keep a tile fresh. Set ttl_seconds to how often the value really changes. A quiet tile should show as stale.
When needs_you is true, say who is asking, what it is about, and the ask.

FAQ

Which pane turns amber?

Production. When the latest production deployment failed, the agent sets needs_you. Preview deploys stay in the feed.

Does this run on the Free plan?

Yes. Every tile in this recipe is a Free type. A Free workspace still has one board and 8 live tiles. Using this recipe adds the sample tiles to that board.

Does Botopticon store the Vercel key?

Botopticon never stores this key. Paste it into the agent, cron host, or MCP config. Revoke it any time.

How does the board stay current?

Your agent fetches the source and posts when a number changes. Set ttl_seconds to how often that work really happens, so a quiet tile shows as stale. Use a timer only for data no agent touches, and then at most daily. Never post the same content again just to keep a tile fresh.

Related

• Stripe revenueStripe · Free
• GitHub shipGitHub · Free
• Cursor agentsCursor · Free