Vercel Connect(https://vercel.com/connect)(https://vercel.com/connect) now lets apps and agents built in v0 securely connect to Slack, Google, Notion, GitHub, Salesforce, and more than 100 other services, Vercel announced on August 21, 2026. The update replaces manually managed API keys with short-lived, automatically refreshed tokens, letting developers connect apps to Slack and other platforms without registering an OAuth application themselves.
The update was published under engineer Vishal Yathish, with contributors Ben Sabic and Hedi Zandi, and it targets developers who want to connect apps to Slack, Notion, GitHub, and similar tools without wiring up OAuth flows by hand. Vercel Connect issues short-lived tokens at runtime instead, an approach the company lays out in full in its original changelog post.
The feature is still in beta, and Vercel has already shown two examples built on top of it: a voice-controlled browser agent from a developer at KERNEL, and an internal dashboard that pulls Slack messages, a Gmail inbox, and Linear tickets into one prioritized digest.
What Is Vercel Connect?
Vercel Connect(https://vercel.com/connect)(https://vercel.com/connect) is the connection layer Vercel built for production AI agents. Agents need access to external systems, but every added service means another API key to store, rotate, and protect. Vercel Connect replaces those long-lived secrets with a connector model. A connector is a registered link to a provider, such as Slack or GitHub, that a team sets up once and reuses across every project. An installation is the provider-side counterpart, tied to a specific workspace, like one company's Slack instance or GitHub organization. When an app or agent needs access, it requests a token at runtime, scoped to a project, environment, installation, and set of permissions. Vercel issues that token on demand and refreshes it automatically, so nothing sensitive sits in an environment variable waiting to leak. For managed connectors including Slack and GitHub, Vercel also handles provider-side app registration, removing a setup step developers previously had to complete themselves.
Inside v0, this connector layer is what makes it possible to connect apps to Slack, Google, and dozens of other services without leaving the chat interface. Connectors belong to a team rather than a single project, so once someone sets one up, every app that team builds afterward can reuse it.
How Do You Connect a v0 App to Slack or Google?
Setting up a connection starts with a prompt, not a settings page. Describe the app or agent, and v0 handles the wiring:
- v0 identifies which services the app needs and asks for approval before proceeding.
- A setup card opens the provider's authorization flow directly in the browser.
- Once sign-in finishes, the chat resumes and v0 keeps building with the connection already attached.
- The connection is saved to the team, so future apps can connect apps to Slack or any other configured service instantly, without repeating setup.
v0 also chooses between two ways an app can act on a service, and tells the developer which one before setup. In the first, each person who uses the app authorizes the service themselves and the app only sees their own data and permissions — useful for something like a dashboard of a user's own GitHub pull requests. In the second, one shared app credential acts on behalf of the whole app, which is how scheduled bots and always-on agents typically run. Full setup details are covered in v0's Vercel Connect documentation.
Vercel Connect vs. Environment Variables
Which Services Does Vercel Connect Support?
The service catalog goes well beyond Slack and Google. Vercel Connect ships dedicated connectors for GitHub, Linear, Discord, Notion, Salesforce, Figma, Snowflake, and WorkOS, alongside generic OAuth and API Key connector types that cover any provider using those standards. The broader library, browsable in Vercel's connector directory, lists more than 100 services, including Asana, HubSpot, Stripe, Shopify, Zoom, Datadog, Jira, Airtable, and model providers like OpenAI, Anthropic, and Hugging Face. Pricing runs on token requests rather than seats or connectors. The Hobby plan includes 5,000 token requests at no extra cost, while Pro and Enterprise teams pay $3 per 10,000 token requests once they exceed their included allotment. Vercel says Resend, Workday, and Microsoft Teams connectors are coming soon, and webhook trigger forwarding — currently limited to Slack — is available in beta, letting Connect forward incoming Slack events to as many as three destination projects per connector.
A Real-World Example: A Voice-Controlled Browser Agent and a Personal Dashboard
Vercel highlighted two early projects built on the new connectors. Danny, from the KERNEL team, used v0 and Vercel Connect to build a voice-controlled browser agent that generates Playwright code on the fly to operate a real browser. Separately, Vercel's own team built a personal dashboard that pulls Slack messages, a Gmail inbox, and Linear tickets into a single view, then produces a digest of what needs attention.
Vercel's own example prompt for the dashboard illustrates the kind of request v0 is built to handle: build a personal dashboard combining Slack, Gmail, and Linear in one view, rank items by whether someone is waiting on a reply — direct mentions, assigned issues nearing their due date, or quiet threads — and show a one-line reason each item surfaced, with a link back to its source. That single instruction now pulls from three separate connectors instead of three separately wired API integrations.
What Are the Current Beta Limitations?
Vercel Connect inside v0 is explicitly labeled a beta feature, and Vercel is asking developers to report bugs through the in-app feedback button rather than treating it as production-hardened. Several specific limits apply today:
- Webhook trigger forwarding works only with Slack for now, even though many other connectors support inbound events.
- Connector branding fields, once set, cannot be fully cleared afterward.
- Token revocation and token lifetime depend on what each individual provider supports, so behavior varies by service.
Why This Matters for AI Agent Development
Vercel Connect arrives as the wider industry works through the same problem from different angles: how do you let an autonomous agent reach real systems without handing it a permanent, over-privileged credential? AWS took a similar approach recently, publishing a four-scope maturity model for agent tool governance through Amazon Bedrock AgentCore Gateway. Automox has moved in a related direction, launching a hosted MCP server that lets AI assistants manage endpoints without local installs. The common thread is credential scope: short-lived, auditable access instead of static keys sitting in a config file.
That urgency tracks with broader adoption data. As BriefFlash has reported, agentic AI is moving into enterprise workflows faster than many organizations can build the governance and cost controls to support it. A connector layer that ships token scoping, automatic refresh, and centralized revocation by default addresses one piece of that gap directly, though it doesn't resolve broader questions around cost controls, auditing, or how teams monitor what an agent actually did with the access it was granted.
For now, Vercel Connect remains in beta, and its immediate relevance is narrower: developers building on v0 who want their generated apps to connect apps to Slack, Google, or any of the other 100-plus supported services without hand-rolling OAuth flows or storing secrets themselves.
Key Takeaways
- Vercel Connect now supports 100+ services, including Slack, Google, Notion, GitHub, and Salesforce, inside v0 apps and agents, as of the August 21, 2026 update.
- Managed connectors like Slack and GitHub skip manual OAuth app registration; Vercel issues short-lived, auto-refreshed tokens instead of stored API keys.
- Connectors are set up once per team and reused across every app; v0 supports both per-user authorization and a shared 'bot' account model.
- Pricing is usage-based: 5,000 free token requests on Hobby, then $3 per 10,000 requests on Pro and Enterprise; the feature is still in beta with Slack-only webhook forwarding for now.
FAQ
What is Vercel Connect?
Vercel Connect is Vercel's connection layer for AI agents and apps. Instead of storing long-lived API keys as environment variables, it issues short-lived, scoped tokens at runtime, and handles OAuth app registration for managed connectors like Slack and GitHub.
How much does Vercel Connect cost?
Pricing is based on token requests. The Hobby plan includes 5,000 token requests at no extra cost. Pro and Enterprise plans are billed $3 per 10,000 token requests once usage exceeds the included allotment.
Which services can a v0 app connect to?
Vercel Connect lists more than 100 services, with dedicated connectors for Slack, GitHub, Linear, Discord, Notion, Salesforce, Google, Figma, Snowflake, and WorkOS, plus generic OAuth and API Key connectors for other providers. Resend, Workday, and Microsoft Teams connectors are listed as coming soon.
