# Introducing Vercel Connect By Steven Van · 2026-06-17 The public beta replaces long-lived provider tokens with short-lived credentials agents request at runtime, covering Slack, GitHub, Notion and more. [Vercel]() has launched [Vercel Connect]() in Public Beta, replacing long-lived provider tokens stored in environment variables with short-lived, scoped credentials that agents request at runtime. An app proves its identity to Connect and gets back a credential scoped to the task, instead of holding a permanent token with full access to everything it might ever need. - A connector to a provider like Slack or GitHub is registered once, from the dashboard or the CLI, then attached to the projects and environments that need it. - The **@vercel/connect** SDK requests a credential at runtime for immediate use against the provider's API, so no provider secret sits in the app. - Dedicated connectors cover Slack, GitHub, Linear, Discord, Notion, Salesforce, Figma, Snowflake and WorkOS, plus generic OAuth and API Key connectors; Resend, Workday and Microsoft Teams are coming soon. - Webhook trigger forwarding is currently Slack-only, sending incoming webhooks to up to three destination projects per connector. - The **Hobby** plan includes 500 token requests and 1,000 trigger forwards free; the **Pro** plan bills $3.00 per 1,000 token requests and $0.95 per 1,000 trigger forwards. [![]()]() ![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 Introducing Vercel Connect on Creators Toolbox]() --- Canonical source: https://creatorstoolbox.com/blog/vercel-introducing-vercel-connect