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.
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 |
{"deployment_id": "e.g. dpl_abc123 or my-app-abc123.vercel.app"}
{"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.
Any of these apps can fire this action as part of a workflow.