Vercel Connect now supports Custom Environments

now lets you link a connector to a so deployments there can request provider tokens and receive forwarded webhooks.Vercel ConnectCustom Environment

Custom Environments appear alongside Production, Preview, and Development when you add or edit a project on a connector in the dashboard.

From the CLI, pass the environment's slug to :--environment

Passing replaces the default environments.--environment

Once linked, a deployment in that environment can request tokens with as usual. If the calling environment isn't on the project link, the request fails with .getTokenClientNotEnabledForEnvironmentError

Trigger destinations can also target a Custom Environment:

Before targeting a Custom Environment with triggers, deploy to it and assign it a verified domain. Vercel Connect forwards events through that domain.

Project links control which deployments can request tokens, and they do not restrict a provider token after it is issued. When environments need provider-level isolation, create a separate connector for each environment and request only the scopes it needs.

Vercel Connect is in beta on all plans. Custom Environments are available on Pro and Enterprise plans. Get started with the or read the .Vercel Connect quickstartstep-by-step guides

Read more