Tool to add an environment variable to a Vercel project. Variables only take effect in subsequent deployments — already-running deployments are not updated. Use after confirming the project exists and you need to configure secrets or configuration values across environments befo…
keyRequiredstringName of the environment variable
slugstringTeam slug to perform the request on behalf of
typeRequiredstringType of the variable storage: 'plain' (non-sensitive values), 'encrypted' (standard encrypted values visible to project users), or 'sensitive' (values that are non-readable once created, only decrypted during builds). NOTE: 'sensitive' type variables can only target 'production'…
valueRequiredstringValue of the environment variable
targetRequiredarrayList of environments where this variable should be available. Must be provided as a list even for a single environment. Valid values: 'production', 'preview', 'development'. NOTE: When type='sensitive', 'development' is NOT allowed - only 'production' and 'preview' are valid tar…
teamIdstringTeam identifier to perform the request on behalf of
upsertbooleanIf true, overwrite existing variables with the same key Silently overwrites without confirmation — only set true when user has explicitly confirmed the existing value should be replaced.
commentstringOptional comment for context
idOrNameRequiredstringThe unique identifier or name of the project
gitBranchstringGit branch to scope this variable to
customEnvironmentIdsarrayList of custom environment identifiers. Must be provided as a list even for a single ID
dataRequiredData from the action execution
errorstringError if any occurred during the execution of the action
successfulRequiredbooleanWhether or not the action execution was successful or not
API key connection. Risk level 2 of 5.
Free Action
No published Skills explicitly reference this Action yet.