Vercel Connect Begins Supporting Custom Environments

Vercel Connect now supports Custom Environment. This allows developers to connect connectors to specific custom environments beyond Production, Preview, and Development, so that deployments in that environment can request provider tokens or receive delivered webhooks.

When using the CLI, you can connect a connector to a specific environment only by passing the environment slug to the --environment option. Once connected, deployments in that environment can request tokens via the getToken method just as before, and requests from environments that are not connected will be blocked with a ClientNotEnabledForEnvironmentError.

Trigger destinations can also target custom environments. To deliver verified webhooks to a specific custom environment, you must first complete a deployment to that environment and assign a verified domain.

Project links control which deployment environments can request tokens, but they do not restrict already-issued provider tokens themselves. Therefore, if strict isolation between environments is required, it is recommended to create a separate connector for each environment and request only the scopes that are needed.