Vercel Connect Now Generally Available on All Plans

Vercel Connect is now generally available (GA) on all plans and v0. Instead of storing long-lived provider secrets, the service adopts an approach where code requests short-lived, scoped tokens at runtime. Deployments authenticate via existing Vercel OIDC identities, and each token is scoped to the task, automatically refreshed, and expires.

You can register service connectors with a single CLI command: vercel connect create. Over 100 preset connectors are available, including Notion, Workday, Slack, GitHub, Linear, Salesforce, Snowflake, and Microsoft, with support for generic OAuth, API key authentication, and MCP servers.

On the security front, tokens are requested only when needed via the getToken function. Changing the subject in the app to a specific user allows the system to act on behalf of that user, triggering an authentication flow if consent is required.

New management features introduced with GA include:

• Granular RBAC: Control permissions for creating and managing connectors
• Audit Logs: Record authentication and connector activity
• Token and Trigger Observability: Monitor token usage across projects

Additionally, triggers can be delivered without stored webhook secrets. Vercel Connect verifies signatures server-side and re-authenticates each event using OIDC identities, delivering events even when deployment protection is enabled. It is also compatible with v0, eve, and Chat SDK, with adapters provided.