Vercel

Move environment variables to and from a Vercel project.

The connection

What	This provider
Vendor	Vercel
Key	`vercel-env`
Availability	`available`. You can connect it today.
Credential penv holds	`vercel-token`
Values read back	yes
Activation	`on-next-deploy`

Direction	What it does
`import`	Reads names and values out of the store into penv.
`export`	Writes names and values from penv into the store.

on-next-deploy. A new value waits there and arrives with your next deploy.

Direction	Policies you can pick
`import`	`skip_existing`, `new_version`, `fail`
`export`	`create_only`, `overwrite`, `overwrite_and_prune`

How syncs work says what each one does.

You paste a credential you already hold. penv seals it and never shows it again.

Field	Label	Kind	Required	What it is
`token`	Access token	secret, masked here and sealed	yes

Fixed when you connect, and shared by every mapping on it.

Field	Label	Kind	Required	Advanced	What it is
`teamId`	Team ID	text	no	yes	Only for a team account. Leave empty to use the token's own scope.

Answered once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`projectId`	Project	text	yes	no	The project whose variables this environment maps onto.
`target`	Deployments	choice	yes	yes	Which deployments read these variables. One of Production, Preview, Development. Starts at `production`.
`gitBranch`	Git branch	text	no	yes	Preview only: pin the variables to one branch.
`customEnvironmentId`	Custom environment	text	no	yes	Adds this environment to the deployments above; one variable serves both. Inside one, VERCEL_ENV reads preview and the name is in VERCEL_TARGET_ENV.

penv probes for these when it verifies the connection.

Permission	Directions	Blocking	Without it
`user:read`	every direction	yes	We cannot confirm which Vercel account this token belongs to.
`projects:read`	every direction	yes	Preview cannot list the project's variable names.
`env:read`	`import`	yes	Import cannot read variable values.
`env:write`	`export`	yes	Export cannot write anything.