ActionVercelUpdated September 2026

How do I check the status of a Vercel deployment?

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

Get Deployment in Vercel — start free All 4 Vercel actions

Get 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
Deployment ID or URL deployment_id	string	Required	Deployment ID or URL. Example: dpl_abc123 or my-app-abc123.vercel.app

Sample request

{
  "deployment_id": "e.g. dpl_abc123 or my-app-abc123.vercel.app"
}

Returns

{
  "id": "dpl_abc123",
  "url": "my-app-abc123.vercel.app",
  "meta": {
    "githubCommitRef": "main",
    "githubCommitMessage": "Update homepage"
  },
  "target": "production",
  "readyState": "READY"
}

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

Triggered by

Apps that pair well as the trigger for Get 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 Get Deployment.

What does the Get Deployment action do in Vercel?

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

What inputs does Get Deployment require?

Required: Deployment ID or URL. 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 Get Deployment support batch operations?

Run Get 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

Create Deployment

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.

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.

Get Deployment in Vercel — start free