Get Deployment: Vercel action

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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Deployment support batch operations?

Yes. Run Get Deployment inside a Loop node to process arrays. Tiny Command handles Vercel's rate limits automatically so you don't have to throttle manually.

More actions