Beta
Vercel Connect forAI apps and agents
Securely connect agents to the tools, data, and services they need to take action.
Copy starter prompt
The connection layer for production agents
Agents need access to external systems, but managing credentials, OAuth apps, scopes, and token exchange adds complexity. Vercel Connect gives teams a secure foundation for connecting agents to the services they rely on.
import { getToken } from '@vercel/connect';
const token = await getToken({ connector: 'slack',});
await slack.chat.postMessage({ token, channel: '#support', text: 'New customer request received',});Secure credentials for agent workflows.
Use short-lived, scoped tokens instead of long-lived secrets. Keep access controlled across projects and environments.
Request credentials at runtime.
Create and manage connectors from Vercel, then request credentials when your app or agent needs them.
Built for agents that take action.
Connect agents to services like Slack, GitHub, and Notion so they can read context and trigger workflows.
Centralized connection management.
Manage all third-party connections in one place across your team, projects, and environments.
Get started
Create a connector and request scoped tokens in minutes.
Create a connector with Vercel Connect in a single command.
$ vercel connect create slack --name acme-slackRequest a short-lived, scoped token from your app or agent — no long-lived secrets to manage.
Frequently asked questions
What is 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.
What problem does Vercel Connect solve?
It removes long-lived third-party secrets from your runtime while still letting agents act on external APIs. You register a connector for a provider, link it to projects and environments, request provider tokens at runtime, and keep an audit trail of authorization and token usage.
How does Vercel Connect work?
Connect uses a connector model. A connector is a registered third-party connection your team can reuse, and an installation is a provider-side install for a specific tenant, such as a Slack workspace or GitHub organization. At runtime you make a token request — optionally scoped with an installation, scopes, resources, and authorization details — bound to specific projects and environments.
Which connectors are available?
Connect supports generic OAuth and API Key connectors, plus dedicated connectors for Slack, GitHub, Linear, Discord, Notion, Salesforce, Figma, Snowflake, and WorkOS. Resend, Workday, Microsoft Teams and more are coming soon.
When should I use Vercel Connect instead of Integrations?
Use Vercel Integrations for 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 — for example, an agent that needs project-scoped access to a Slack workspace.
How does pricing work?
Pricing is based on token requests. The Hobby plan includes 5K token requests at no additional cost. On the Pro and Enterprise plans, token requests are billed at $3 per 10K token requests.
Does Vercel Connect support webhook triggers?
Yes. Webhook trigger forwarding is available in Beta and is currently Slack-only. When enabled, Connect can forward incoming Slack webhooks to up to three destination projects per connector.
What are the current Beta limitations?
Trigger forwarding is Slack-only, connector branding fields cannot be fully cleared after you set them, and token revocation and token lifetime depend on provider support.
