---
title: Vercel Connect
description: Connect your v0 apps and agents to third-party services – no API keys required.
product: v0
type: integration
prerequisites:
  - /docs/quickstart
related:
  - /docs/external-apis
  - /docs/databases
  - /docs/full-stack-apps
---

# Vercel Connect



<Callout>
  Vercel Connect in v0 is currently in **beta**. If you encounter bugs while using this experimental feature, please report them to the v0 team using the in-app feedback button.
</Callout>

v0-generated apps and agents can access third-party services – Slack, GitHub, Notion, Salesforce, and more – through [Vercel Connect](https://vercel.com/docs/connect). You authorize a service once in your browser, and your app receives short-lived, automatically refreshed tokens at runtime. There are no API keys to find, paste, rotate, or leak.

## Connect vs. environment variables

Vercel Connect replaces pasted API keys and static environment variables with short lived, managed credentials issued to your app at runtime. See [Introducing Vercel Connect](https://vercel.com/blog/introducing-vercel-connect).

|                      | Environment variables           | Vercel Connect                                              |
| -------------------- | ------------------------------- | ----------------------------------------------------------- |
| **Credential**       | A static key pasted per project | OAuth tokens issued and refreshed for you                   |
| **Acts as**          | One shared key for everyone     | Each signed-in user, or a shared app identity               |
| **Receiving events** | You configure provider webhooks | Verified webhooks delivered to your app by Connect          |
| **Rotation**         | Manual                          | Automatic refresh; revoke anytime from the dashboard or API |

Keep [environment variables](/docs/external-apis) for configuration that isn't a service credential.

## What you can build

* **Apps that act as the signed-in user.** *"Build me a dashboard of my open GitHub pull requests."* Each viewer authorizes GitHub themselves and sees their own data, with their own permissions.
* **Agents that work your tools.** *"Build me a Slack agent that sends me a daily summary of my merged PRs."* v0 connects Slack and GitHub, and the agent posts on schedule.
* **Bots that respond to events.** Connect delivers the service's webhooks (Slack mentions, messages, DMs, etc.) straight to your app. You never touch the provider's webhook settings.

## Setting up a connection

Describe what you want to build; v0 handles the wiring.

1. v0 proposes the services it needs and asks for your approval.
2. A setup card opens the authorization flow in your browser, where you sign in to the service.
3. When you finish, the chat resumes and v0 keeps building with the connection attached.

## Whose account does the app use?

v0 chooses between two authorization models based on what you asked for, and tells you which before setup:

* **Your users' accounts** – each person authorizes the service themselves, and the app acts with their permissions. The first time someone uses the feature, they're prompted to sign in in the app, or as a button right in Slack.
* **A shared app account** – one credential the whole app acts through, as itself; this is how bots and scheduled agents run. Everyone using the app shares its access.

## Managing connections

The connections attached to a project are listed in **Project menu** → **Settings** → **Integrations**, with links out to each Connect client in the Vercel dashboard. From the [Connect dashboard](https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fconnect\&title=Go+to+Vercel+Connect) you can revoke access and review event delivery.

Tokens are encrypted and short-lived, and never appear in your code, environment variables, or chat.

<LearnMore href="https://vercel.com/docs/connect" icon="arrow">
  Learn more about Vercel Connect
</LearnMore>


---

For a semantic overview of all documentation, see [/docs/sitemap.md](/docs/sitemap.md)

For an index of all available documentation, see [/docs/llms.txt](/docs/llms.txt)

For agent-facing discovery, including API and MCP surfaces, see [/docs/agents.md](/docs/agents.md)