--- title: Connectors product: vercel url: /docs/connect/concepts/connectors canonical_url: "https://vercel.com/docs/connect/concepts/connectors" last_updated: 2026-07-31 type: conceptual prerequisites: - /docs/connect/concepts - /docs/connect related: - /docs/connect - /docs/connect/legal - /docs/cli/connect - /docs/connect/concepts/installations - /docs/connect/concepts/project-links summary: A connector is the team-owned record that represents one third-party service. Its type determines which capabilities are available. install_vercel_plugin: npx plugins add vercel/vercel-plugin --- # Connectors A **connector** is the team-owned record that represents one third-party service inside Vercel Connect. Each connector has a type that determines how Vercel Connect authenticates to the provider and which capabilities (installations, triggers, revocation) are available. ## 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) — 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) — Authenticate Slack, GitHub, and Linear adapters with Vercel Connect — short-lived runtime tokens for outbound calls and - [Build an integrations hub with Nuxt and Vercel Connect](https://vercel.com/kb/guide/nuxt-and-vercel-connect?from=related) — Build an Integrations Hub with Nuxt and Vercel Connect. Connect GitHub and Linear over OAuth and mint short-lived tokens - [Authentication](https://vercel.com/docs/connect/concepts/authentication?from=related) — Every Vercel Connect token request has two legs that both have to authenticate: the caller calling Vercel Connect, and V - [SDK Reference](https://vercel.com/docs/connect/ts-sdk-reference?from=related) — API reference for @vercel/connect, the TypeScript SDK for requesting runtime tokens from Vercel Connect. - [Tokens](https://vercel.com/docs/connect/concepts/tokens?from=related) — Short-lived provider credentials issued by Vercel Connect. Each token request specifies a subject, optional installation Full cross-link map for this page: [/docs/connect/concepts/connectors.graph.md](/docs/connect/concepts/connectors.graph.md) ## Identifiers Each connector has four identifiers: - **`uid`**: a stable, human-readable string that you choose at create time and use everywhere else (in `getToken`, in CLI commands, in the dashboard URL). Example: `slack/acme-slack` or `oauth/linear`. - **`id`**: an opaque internal identifier that Vercel Connect uses in API responses. You rarely use it directly. - **`type`**: the connector type. Determines the auth flow and the available capabilities (`slack`, `github`, `oauth`, `snowflake`, `salesforce`, `api-key`, `custom`). - **`service`**: the specific provider the connector targets. For built-in types this matches the type (`slack`, `github`). For typed-but-generic connectors like Custom OAuth, this is the service URL or name. Example: `type: 'oauth'`, `service: 'mcp.linear.app'`. When you call `getToken('slack/acme-slack', ...)`, the string `slack/acme-slack` is the connector's `uid`. ## Connector types | Type | Auth model | Multi-tenant installations | Triggers | | ------------ | --------------------------------------------------------------------------------------- | -------------------------- | -------- | | Slack | Slack app install (per workspace) | yes | yes | | GitHub | GitHub app install (per org or user) | yes | yes | | Linear | Linear app install (per workspace) | yes | yes | | Snowflake | Snowflake Partner Connect JWT | no | no | | Salesforce | Managed OAuth flow | no | no | | API Key | Static credential supplied at create time | no | no | | Custom OAuth | OAuth 2.0 / OIDC against any URL-identified service; authorization-code flow with PKCE and/or client-credentials flow | no | no | The capability matrix above is the current beta set and may change. Connector types may be added or removed without notice. New types are added behind feature flags; check the dashboard for what's available to your team. ## Setting up a custom OAuth connector Slack, GitHub, Snowflake, Linear, and Salesforce are [Vercel Managed Connectors](/docs/connect#managed-connectors): Vercel registers the OAuth app, and you authorize it to access your account or workspace. For any other provider, you can create a **Custom OAuth** connector, and Vercel does as much of the setup as the provider supports: - **Discover endpoints from a URL**: Enter a server URL, such as `mcp.linear.app`, and Vercel reads the provider's published OAuth metadata to fill in the authorization and token endpoints. - **Bring your own client**: Add the client ID and client secret from the OAuth app you registered with the provider. - **Let Vercel register the client**: When a provider supports automatic client registration, [Vercel Assisted Setup](/docs/connect/legal#4.-vercel-assisted-setup) creates the OAuth client for you, so you don't need to register an app or manage a client secret. ## Connection methods Vercel already knows how to connect to many services. When you create a connector, search for the service by name. For a **known service**, Vercel fills in what it knows and you only supply what is specific to your account: - **OAuth**: Vercel fills in the authorization and token endpoints and the provider's default scopes. You add your client ID and secret, or let [Vercel Assisted Setup](/docs/connect/legal#4.-vercel-assisted-setup) register the client where the provider supports it. - **API key**: Vercel links you to where the provider issues keys. Generate the key there, then paste it into the connector when you create it. A known service publishes one or more **connection methods**: the distinct ways you can connect to it. When a service publishes several, they differ in who registers the application (Vercel, through [Vercel Assisted Setup](/docs/connect/legal#4.-vercel-assisted-setup), or you) and in which product you connect to, such as a REST API or an MCP server. Known services work in the dashboard and from the CLI. Running [`vercel connect create `](/docs/cli/connect#vercel-connect-create) prompts you for the product, the connection method, and the credentials that method needs, so you can create a connector without leaving the terminal. Run `vercel connect create --help` to see what a service supports. ## Branding A connector carries a name, an icon, and accent and background colors. Slack propagates the icon to the workspace. Other providers may display branding on their login and consent screens, or only inside the Vercel dashboard. ## Lifecycle Connectors are created, updated, and deleted by team members through the dashboard or the [`vercel connect`](/docs/cli/connect) CLI. A connector has no time-to-live: unless you delete it, it lives indefinitely. Deletion is soft by default; a deleted connector cannot serve new token requests, and you can permanently remove it with `vercel connect remove --disconnect-all`. ## Next steps - [Installations](/docs/connect/concepts/installations): How one connector serves many tenants. - [Project links](/docs/connect/concepts/project-links): How a connector is bound to projects and environments. - [Quickstart](/docs/connect/quickstart): Create your first connector end to end. --- [View full sitemap](/docs/sitemap)