List Deployments: 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
Project ID or Name projectId	string	Optional	Project ID or Name. Example: my-app
Target target	options	Optional	Target. Options: All, Production, Preview
Limit limit	string	Optional	Limit. e.g. "20"

Sample request

{
  "projectId": "e.g. my-app",
  "target": "{{trigger.target}}",
  "limit": "20"
}

Returns

{
  "deployments": [
    {
      "uid": "dpl_abc123",
      "url": "my-app-abc123.vercel.app",
      "state": "READY",
      "target": "production",
      "created": 1700000000000
    }
  ]
}

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

FAQ

Questions about List Deployments.

What does the List Deployments action do in Vercel?

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

What inputs does List Deployments require?

List Deployments has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List Deployments support batch operations?

Yes. Run List Deployments 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