ActionVercelUpdated September 2026

How do I trigger a new Vercel deployment?

Short answer: You can create deployment in Vercel by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Vercel Create Deployment action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create Deployment in Vercel — start free All 4 Vercel actions

Create Deployment in Vercel — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Project Name name	string	Required	Project Name. Example: my-app
Git Ref gitSource_ref	string	Required	Branch, tag, or commit SHA to deploy
Repository ID gitSource_repoId	string	Required	GitHub/GitLab repo ID (numeric)
Git Provider gitSource_type	options	Required	Git Provider. Options: GitHub, GitLab, Bitbucket
Target target	options	Optional	Target. Options: Production, Preview

Sample request

{
  "name": "e.g. my-app",
  "gitSource_ref": "e.g. main",
  "gitSource_repoId": "e.g. 123456789",
  "gitSource_type": "{{trigger.gitSource_type}}",
  "target": "{{trigger.target}}"
}

Returns

{
  "id": "dpl_abc123",
  "url": "my-app-abc123.vercel.app",
  "target": "production",
  "createdAt": 1700000000000,
  "readyState": "QUEUED"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Create Deployment.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Vercel

2 Google Sheets triggers

HubSpot → Vercel

18 HubSpot triggers

FAQ

Questions about Create Deployment.

What does the Create Deployment action do in Vercel?

Triggers a new deployment for a Vercel project from a Git ref or uploaded files. Use to re-deploy on content-only changes (CMS publishes) or to promote from a non-Git workflow.

What inputs does Create Deployment require?

Required: Project Name, Git Ref, Repository ID, Git Provider. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Vercel returns an error?

The run history shows the failed step with its input and the error message Vercel returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create Deployment support batch operations?

Run Create Deployment inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Vercel's rate limits.

More actions

Other Vercel actions.

Action

Get Deployment

Returns full details about a specific Vercel deployment: state (READY/ERROR/BUILDING), URL, environment, and creator. Poll this after Create Deployment until READY.

Action

List Deployments

Lists recent Vercel deployments for a project, with ref, environment, state, and timing. Used in release dashboards and audit logs.

Action

List Projects

Lists all projects in the connected Vercel account with their framework, latest deployment, and Git source. Used as the first step in cross-project automation.

Create Deployment in Vercel — start free