- Integrations
- /
- Vercel
- /
- Actions
- /
- Get Deployment
ActionVercelUpdated May 2026
How do I check the status of a Vercel deployment?
Short answer: Drop the "Vercel → Get Deployment" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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
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.
ActionList Deployments
Lists recent Vercel deployments for a project, with ref, environment, state, and timing. Used in release dashboards and audit logs.
ActionList 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.
Send get deployment from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.