Vercel Deployments icon

Vercel Deployments

Manage Vercel deployments via the Vercel REST API

Actions8

Create Deployment

AI-generated

Summary

Creates a new Vercel deployment for an existing project via POST /v13/deployments, from either a Git source or prebuilt files, and returns the Vercel API response for the new deployment.

Inputs

  • Name (Project Name) (required) — Name of an existing Vercel project to deploy.
  • Target — Deployment target: production (default), preview, or staging.
  • Git Source — Type (GitHub/GitLab/Bitbucket), Org, Repo, Ref (defaults to main) and optional SHA. Only sent if a type is set and Org or Repo is filled in.
  • Project Settings — Optional overrides: framework, build command, install command, output directory, dev command, root directory. Empty values are omitted.
  • Prebuilt — When enabled, sends a list of files instead of relying on a Git source.
  • Prebuilt Input Mode — Shown when Prebuilt is on. Choose Manual (UI file list) or JSON (array).
  • Files (Prebuilt) — Manual mode: list of entries with file path, data (string contents or public http(s) URL) and optional base64 encoding. At least one file is required.
  • Files JSON — JSON mode: array of objects with file, data and optional encoding. Must be a non-empty array, and each item needs file and data.
  • Environment Variables (override) — Name/value assignments sent as env for this deployment only. They are not saved on the project.

Output shape

One output item per input item, containing the raw JSON response from the Vercel create-deployment API (deployment id, url, state and similar fields).

Data values that start with http(s):// are downloaded by the node and re-encoded as base64 before upload. The team ID comes from the credential, or from a teamIdOverride parameter if one is present. That parameter isn't declared in this operation's properties. It is sent in the body and in the query string. With Continue On Fail enabled, failures return an item with json.error. Otherwise the node throws an error.

Examples

Example 1: Deploy the main branch of a GitHub repo to production after a webhook fires.

Name=my-app, Target=Production, Git Source: type=github, org=my-org, repo=my-repo, ref=main.

Example 2: Publish a static page generated earlier in the workflow as a preview deployment.

Name=my-site, Target=Preview, Prebuilt=true, Input Mode=JSON, Files JSON set by expression with index.html contents.

Example 3: Deploy with a one-off environment override.

Name=my-app, Git Source set, Environment Variables: FEATURE_FLAG=on.

Links

Discussion