Create Vercel project env variable
Approval-gated Vercel environment-variable creation workflow. It reads existing environment-variable metadata with decrypt=false, then creates exactly one project environment variable through recued-core.vercel.project.env.create. It never reads secret values, updates or removes existing variables, creates deployments, mutates domains, pauses projects, deletes records, or calls arbitrary Vercel APIs.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (18 steps)
project_id_or_name_trim
trim
Trim whitespace from setting project id or name
key_trim
trim
Trim whitespace from setting key
type_trim
trim
Trim whitespace from setting type
git_branch_trim
trim
Trim whitespace from setting git branch
comment_trim
trim
Trim whitespace from setting comment
team_id_trim
trim
Trim whitespace from setting team id
team_slug_trim
trim
Trim whitespace from setting team slug
reason_trim
trim
Trim whitespace from setting reason
has_project
compare
Check if project id or name trim has data
has_key
compare
Check if key trim has data
ready
all
Check if all conditions are true
project
?
existing_env_raw
?
create_env
?
skip: step.ready not_equal true
existing_env
default
Apply default
existing_count
count
Count items in existing env
env_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
key
setting
=
type
setting
=
encrypted
value
setting
=
reason
setting
=
target
setting
=
preview,production
upsert
setting
=
false
vercel
setting
=
comment
setting
=
team id
setting
=
team slug
setting
=
git branch
setting
=
project id or name
setting
=
custom environment ids
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.