---
title: Connect
product: vercel
url: /docs/connect
canonical_url: "https://vercel.com/docs/connect"
last_updated: 2018-10-20
type: conceptual
prerequisites:
  []
related:
  - /docs/connect/getting-started
  - /docs/integrations
  - /docs/cli/connect
summary: Learn about connect on Vercel.
install_vercel_plugin: npx plugins add vercel/vercel-plugin
---

# Vercel Connect

Vercel Connect lets your agents and services access external systems on behalf of your users and teams. Instead of storing provider credentials in long-lived environment variables, you request user-authorized tokens at runtime with project-level access controls.

> **🔒 Permissions Required**: Vercel Connect

For a first setup path, see [Getting Started with Vercel Connect](/docs/connect/getting-started).

## What Vercel Connect solves

Vercel Connect helps you remove long-lived third-party secrets from your runtime while still letting agents act on external APIs.

With Vercel Connect, you can:

- Register a connector for a provider
- Link that connector to one or more projects and environments
- Request provider tokens at runtime
- Keep an audit trail of authorization and token usage

## How Connect works

Vercel Connect uses a connector model:

| Concept | Description |
| --- | --- |
| Connector | A registered third-party connection that your team can reuse |
| Installation | A provider-side installation for a specific tenant, such as a Slack workspace or GitHub organization |
| Token request | A token request can include options such as `installationId`, `scopes`, `resources`, and `authorizationDetails` |
| Client-project link | The connector to project binding, including enabled environments |

## Available connectors in Beta

The dashboard currently includes:

- **Slack**
- **GitHub**
- **Generic OAuth**

Your team may also see additional connector types in feature-flagged Beta flows.

## Trigger forwarding in Beta

Webhook trigger forwarding exists in Vercel Connect, but it is currently Slack-only in Beta.

When enabled, Vercel Connect can forward incoming Slack webhooks to up to three destination projects per connector.

## When to use Vercel Connect or integrations

Use [Vercel Integrations](/docs/integrations) when you want marketplace-managed installs and provider-managed products in the Vercel Marketplace.

Use Vercel Connect when you need delegated runtime credentials and user authorization for agent workflows. Common examples include:

- Running an agent that needs project-scoped access to a Slack workspace
- Linking one connector to multiple Vercel projects and environments
- Requesting user-authorized provider tokens at runtime instead of storing long-lived provider secrets

## Known Beta limitations

- Trigger forwarding is Slack-only
- Connector branding fields cannot be fully cleared after you set them
- Token revocation and token lifetime depend on provider support

## Related docs

- [Getting Started with Vercel Connect](/docs/connect/getting-started)
- [Vercel Integrations](/docs/integrations)
- [vercel connect](/docs/cli/connect)


---

[View full sitemap](/docs/sitemap)