# Vercel Connect: Secure access to external services for your agents By Steven Van · 2026-06-17 Vercel Connect issues short-lived, scoped tokens to agents at runtime for Slack, GitHub, Salesforce and custom APIs, no stored secrets required. Vercel Connect lets apps and agents deployed on [Vercel]() reach external services like Slack, GitHub, and Salesforce, or your own custom APIs, without storing a long-lived provider secret in the environment. You register a connector once, from the dashboard or the CLI, and your code requests a scoped, short-lived token from it at runtime, only when it needs one. The SDK fetches and refreshes that token automatically, so there's no secret to store or rotate by hand. - Tokens are scoped to the task in front of them, with granularity that depends on the provider: a GitHub token can be limited to a single repository and read-only access, instead of the whole organization. - A token can also be tied to a specific user rather than the app itself. It then acts with that user's identity and inherits only their permissions. - A connector only works in the environments it's attached to, so separate connectors can be run for development, preview, and production, and a token leaked in development can't be used against production. Read the full details in the [Vercel Connect documentation](). [![]()]() ![Vercel]() Vercel The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config. [View Vercel →]() Sources [Original source]() [Read Vercel Connect: Secure access to external services for your agents on Creators Toolbox]() --- Canonical source: https://creatorstoolbox.com/blog/vercel-vercel-connect-secure-access-to-external-services-for-your-agents