> For the complete documentation index, see [llms.txt](https://notara.gitbook.io/notara-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notara.gitbook.io/notara-docs/connectors/vercel.md).

# Vercel

The Vercel connector gives the agent visibility into your deployments — checking build status, reading failure logs, and listing projects and domains without leaving Slack.

## What It Enables

| Tool                    | Capability | Description                                                         |
| ----------------------- | ---------- | ------------------------------------------------------------------- |
| `list_projects`         | `read`     | List projects in your Vercel scope, filterable by name              |
| `list_deployments`      | `read`     | List recent deployments; filter by project, state, or environment   |
| `get_deployment`        | `read`     | Get one deployment's full detail including error messages           |
| `get_deployment_events` | `read`     | Read the build log for a deployment — use this to diagnose failures |
| `list_domains`          | `read`     | List registered domains and their verification state                |

## Setup

**Required:** Vercel Access Token (personal or team).

**Where to find it:** In Vercel, go to **Account Settings → Tokens** and create a new token. For team scopes, you can also supply a Team ID in the connector settings.

1. In the Notara dashboard, go to **Tools**.
2. Click the **Vercel** tile.
3. Go to [vercel.com/account/tokens](https://vercel.com/account/tokens) and create a token.
4. Paste it into the credential field. Optionally enter your **Team ID** (starts with `team_`) to scope calls to a team.
5. Click **Verify & Save**.

Your token is encrypted at rest with AES-256-GCM.

## Example Prompts

> "Did the last production deploy to the web project succeed?"

> "Why did the most recent build fail? Show me the error logs."

> "List all deployments in the ERROR state from today."


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://notara.gitbook.io/notara-docs/connectors/vercel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.