--- title: Vercel Connect product: vercel url: /docs/connect canonical_url: "https://vercel.com/docs/connect" last_updated: 2026-07-31 type: conceptual prerequisites: [] related: - /docs/connect/quickstart - /docs/connect/concepts - /docs/connect/concepts/connectors - /docs/connect/concepts/tokens - /docs/connect/concepts/authentication summary: Use Vercel Connect to create connectors, authorize provider access, request provider tokens at runtime, and run agent workflows without long-lived... install_vercel_plugin: npx plugins add vercel/vercel-plugin --- # Vercel Connect > **🔒 Permissions Required**: Vercel Connect ## Related pages > **For AI agents:** Follow these links to understand how this page connects to the rest of the Vercel ecosystem. For the full cross-link map (inbound, outbound, prerequisites, and semantic neighbors), see the .graph.md link below. - [Give your agents secure access to third-party APIs](https://vercel.com/kb/guide/vercel-connect?from=related&source_path=%2Fdocs%2Fconnect&source_site=vercel-docs&relationship=related) — Use Vercel Connect to call provider APIs like Slack, GitHub, Linear, Discord, Notion, Figma, Snowflake, and Salesforce f - [Vercel Connect](https://chat-sdk.dev/docs/vercel-connect?from=related&source_path=%2Fdocs%2Fconnect&source_site=vercel-docs&relationship=related) — Authenticate Slack, Discord, GitHub, Linear, Notion, and Telegram adapters with Vercel Connect — short-lived runtime tok - [Connections](https://eve.dev/docs/connections?from=related&source_path=%2Fdocs%2Fconnect&source_site=vercel-docs&relationship=related) — Expose external MCP and OpenAPI servers to the model, with connection tokens the model never sees. - [Vercel Connect](https://v0.app/docs/vercel-connect?from=related&source_path=%2Fdocs%2Fconnect&source_site=vercel-docs&relationship=related) — Connect your v0 apps and agents to third-party services – no API keys required. - [Build AI agents with AI Gateway and AI SDK](https://vercel.com/kb/guide/ai-gateway-and-ai-sdk?from=related&source_path=%2Fdocs%2Fconnect&source_site=vercel-docs&relationship=related) — Build AI agents on Vercel with AI Gateway and AI SDK, then make them reliable, capable, and durable with Sandbox, Chat S - [How to build a browser agent that works behind a login](https://vercel.com/kb/guide/build-a-browser-agent?from=related&source_path=%2Fdocs%2Fconnect&source_site=vercel-docs&relationship=related) — Build a browser agent with eve, Vercel Connect, and KERNEL managed auth that signs a user in through a human-in-the-loop - [Build a daily digest bot with Chat SDK and Workflow SDK](https://vercel.com/kb/guide/daily-digest-bot-with-chat-sdk-and-workflow-sdk?from=related&source_path=%2Fdocs%2Fconnect&source_site=vercel-docs&relationship=related) — Build a daily digest bot that posts a daily digest of GitHub stats to Slack. Learn how to use Vercel Connect to set up S - [Draft content in your voice from Slack with eve](https://vercel.com/kb/guide/eve-content-agent?from=related&source_path=%2Fdocs%2Fconnect&source_site=vercel-docs&relationship=related) — Deploy the eve content agent template, a Slack bot that drafts blog posts, LinkedIn posts, release notes, and newsletter - [Environments](https://vercel.com/docs/deployments/environments?from=related&source_path=%2Fdocs%2Fconnect&source_site=vercel-docs&relationship=related) — Environments are for developing locally, testing changes in a pre-production environment, and serving end-users in produ - [eve](https://vercel.com/docs/eve?from=related&source_path=%2Fdocs%2Fconnect&source_site=vercel-docs&relationship=related) — Learn how to deploy and run durable backend AI agents built with the open-source eve framework on Vercel. - [Concepts](https://vercel.com/docs/eve/concepts?from=related&source_path=%2Fdocs%2Fconnect&source_site=vercel-docs&relationship=related) — Learn how eve agents, sessions, channels, tools, skills, connections, and sandboxes fit together. - [Key Management](https://vercel.com/docs/kms?from=related&source_path=%2Fdocs%2Fconnect&source_site=vercel-docs&relationship=related) — Sign JWTs and messages with Vercel-managed signing keys. Learn about issuers, keys, and policies, and how to sign from V Full cross-link map for this page: [/docs/connect.graph.md](/docs/connect.graph.md?from=related&source_path=%2Fdocs%2Fconnect&source_site=vercel-docs&relationship=graph) With [Vercel Connect](/connect), your deployed apps can talk to other services. First, you set up a connection **once** to Slack, GitHub, Microsoft, Snowflake, Salesforce, or any OAuth or API-key service at the team level. Then, any project you allow can use this connection. Your code asks Connect for access at the moment it needs it, so no provider API key ever lives in your environment variables. To create your first connector and request a token, follow the [Quickstart](/docs/connect/quickstart). For the conceptual model, see the [Concepts](/docs/connect/concepts) overview, starting with [Connectors](/docs/connect/concepts/connectors), [Tokens](/docs/connect/concepts/tokens), and [Authentication](/docs/connect/concepts/authentication). ## What you can build - **Call third-party APIs from an agent**: Post to Slack, open GitHub PRs, call Microsoft Graph, query Snowflake, or hit any OAuth- or API-key-protected service without bundling provider secrets into your deployment. - **Act on behalf of your users**: Ask a user to authorize once, then get a refreshable user token that your agent uses to make calls as that user. - **Receive provider webhooks**: Verify and forward signed Slack events to project destinations you control. To do any of these, you [pick a connector](/connect/browse) for the provider you want to reach: - **[Multiple connector types](/connect/browse)**: Browse the available services, connection methods, and capabilities. - **[Token subject types](/docs/connect/concepts/tokens#subject-types)**: Issue tokens that act as your service (`app`), a specific user (`user`), or a federated identity (`jwt-bearer`) from a single connector. - **[Installations and multi-tenancy](/docs/connect/concepts/installations)**: Serve many tenants from one connector, such as Slack workspaces, GitHub organizations, or Microsoft tenants. - **[Fine-grained scoping](/docs/connect/concepts/tokens#scoping-a-token)**: Narrow each token with provider scopes, resource indicators, and rich authorization requests. - **[Refresh and revocation](/docs/connect/concepts/tokens#caching-and-refresh)**: Let tokens refresh automatically, and revoke at the provider when supported. - **[Trigger forwarding](/docs/connect/concepts/triggers)**: Fan out verified webhooks to the project destinations you register on the connector. - **[Connector branding](/docs/connect/concepts/connectors#branding)**: Set a per-connector icon, background color, and accent color. ## How authentication works When your code calls `getToken()`, Vercel Connect authenticates in two directions: your code authenticates to Vercel Connect with a Vercel OIDC token or a Vercel access token, and Vercel Connect exchanges the authorized credential with the provider. ### From your code to Vercel Connect The `@vercel/connect` SDK gives you two ways to authenticate: - **Vercel OIDC token** (recommended): On Vercel, the SDK uses the [OIDC token](/docs/oidc) that Vercel injects into your deployment automatically. Connect verifies the token and checks it against the connector's project links to confirm your project and environment are allowed to request tokens. - **Access token**: For external CI/CD or non-Vercel environments where `VERCEL_OIDC_TOKEN` isn't available, pass a [Vercel access token](/docs/rest-api#creating-an-access-token) to the SDK through the `vercelToken` option on `getToken`. Dashboard and CLI calls authenticate the same way, using your active Vercel session. To pull an OIDC token into `.env.local` for local development, follow the [Quickstart](/docs/connect/quickstart). ### From Vercel Connect to the provider Each connector type has its own provider-side flow: - **Slack** and **GitHub**: Managed app installs, scoped to one workspace or organization per installation. - **Microsoft**: A Microsoft Entra app that Vercel registers in your own Microsoft tenant, installed when a tenant administrator grants it admin consent. - **Custom OAuth**: Managed OAuth against the service's URL, on behalf of the installing user (authorization-code flow) or as your service (client-credentials flow). - **API key**: A credential the connector owner supplies once at create time. Each connector defines its provider-side authentication flow. [Browse connectors](/connect/browse) to compare connection methods and setup instructions. For the full picture, including how token requests are authorized against project links, RBAC for dashboard and CLI calls, the per-connector provider flows, and the error classes thrown on auth failures, see the [Authentication](/docs/connect/concepts/authentication) concepts page. ## Watch what your connectors are doing Every connector includes an **Observability** tab that logs token requests, authorizations, trigger deliveries, and revocations. Filter events by type, environment, project, or subject, and use stable correlation IDs (`tokenId`, `authorizationId`, `triggerRequestId`) to trace each token across events and match them to your own systems. To retain events beyond your plan's retention window, forward them to any custom webhook endpoint by adding a [Drain](/docs/drains) (available on Pro and Enterprise plans). See [Observability](/docs/connect/observability) for the full reference. ## Build with the SDK and CLI - **[SDK Reference](/docs/connect/ts-sdk-reference)**: API reference for `@vercel/connect`, including `getToken`, `getTokenResponse`, the `ConnectTokenParams` and `ConnectTokenResponse` shapes, and the error classes. - **[CLI Reference](/docs/cli/connect)**: Manage connectors, project links, and triggers from the terminal with `vercel connect`. ## Connector ownership models You can connect to these providers. Pick the connector that matches the service you want your agent or service to reach: - **Slack**: Post messages and receive events through a Vercel-developed Slack app, installed per workspace. - **GitHub**: Open PRs and act on repositories through a Vercel-developed GitHub app, installed per organization or user. - **Microsoft**: Call Microsoft Graph and Azure APIs through a Microsoft Entra app that Vercel registers in your own Microsoft tenant. You choose its delegated Graph permissions and application permissions at create time, and can change them later. Your code then requests delegated tokens that act as a signed-in user, or app-only tokens that act as the app itself. App-only tokens, and delegated scopes that Microsoft flags as needing an administrator, require a tenant administrator to grant admin consent once. - **Linear**: Read and write issues through a Vercel-developed Linear app, installed per workspace. - **Snowflake**: Query data through the Snowflake Partner Connect integration. - **Salesforce**: Call your Salesforce org through a Vercel-managed OAuth client. - **Custom OAuth**: Reach any service that supports OAuth or OIDC at a URL you provide. Bring your own client ID and client secret. Supports both the authorization-code flow with PKCE (to act on behalf of a user) and the client-credentials flow (to act as your service). After creating the connector, open it in the dashboard, click **Edit**, and select the grant types you want to enable. - **API key**: Store a static, long-lived API key for providers that issue one. You supply the key at create time. ### Who registers the OAuth client The connectors above fall into two operating models, defined in the [Vercel Connect product terms](/docs/connect/legal#1.-definitions). The model determines who registers the OAuth client (or credential) with the Third Party Platform and what setup work falls to you. - **Vercel Managed Connector**: Vercel registers the OAuth client with the Third Party Platform, and you authorize Vercel's client to access your account or workspace. You do not register an OAuth client or manage client secrets. Slack, GitHub, Linear, Microsoft, Snowflake, and Salesforce use this model. See [Section 3](/docs/connect/legal#3.-vercel-managed-connector) of the Vercel Connect terms. - **Customer Managed Connector**: You register an OAuth client (or generate an API key) with the Third Party Platform yourself and supply the credentials at create time. Vercel stores them and exchanges tokens on your behalf at runtime. You manage those credentials on the provider side. Custom OAuth and API key use this model. For providers that support it, [Vercel Assisted Setup](/docs/connect/legal#4.-vercel-assisted-setup) is a one-off helper action that performs some or all of the OAuth-client registration steps on your behalf when you bootstrap a Customer Managed Connector. Create either kind of connector from the dashboard or with [`vercel connect create`](/docs/cli/connect#vercel-connect-create). For a known service, the CLI prompts you for the [connection method](/docs/connect/concepts/connectors#connection-methods) and any credentials the provider needs, and opens your browser only when the provider requires you to sign in or install an app. [Browse all connectors](/connect/browse) for the current catalog. Each connector page includes authentication methods, trigger support, and setup instructions. ## Pricing Vercel Connect is billed per token request. Hobby includes 500 token requests per month at no extra charge. Pro is billed at $3.00 per 1,000 token requests. Enterprise is billed at your negotiated Enterprise rate. Contact your account team for details. See [Pricing and Limits](/docs/connect/pricing) for the full table, how to stop being billed, and the platform limits. ## When to use Vercel Connect Use Vercel Connect when you need delegated runtime credentials, when the same provider serves multiple Vercel projects or environments, or when an agent needs to act on behalf of a user. Use a [Vercel Integration](/docs/integrations) instead when you want a marketplace-managed install for a provider-billed product. ## Resources **Quickstart**: Create your first connector and request a runtime token in four steps. [Learn more →](/docs/connect/quickstart) **Concepts**: Understand connectors, installations, tokens, project links, triggers, and authentication. [Learn more →](/docs/connect/concepts) **SDK Reference**: API reference for @vercel/connect: getToken, getTokenResponse, errors, and caching. [Learn more →](/docs/connect/ts-sdk-reference) **CLI Reference**: Manage connectors, projects, and tokens with the vercel connect command. [Learn more →](/docs/cli/connect) **Observability**: Monitor token requests, authorizations, triggers, and revocations for each connector. [Learn more →](/docs/connect/observability) **Pricing and Limits**: Plan pricing, how to stop being billed, and platform limits. [Learn more →](/docs/connect/pricing) --- [View full sitemap](/docs/sitemap)