Short answer: Drop the "Vercel → Create Deployment" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Project Name name | string | Required | Project Name. Example: my-app |
Git Ref gitSource_ref | string | Required | Branch, tag, or commit SHA to deploy |
Repository ID gitSource_repoId | string | Required | GitHub/GitLab repo ID (numeric) |
Git Provider gitSource_type | options | Required | Git Provider. Options: GitHub, GitLab, Bitbucket |
Target target | options | Optional | Target. Options: Production, Preview |
{"name": "e.g. my-app","gitSource_ref": "e.g. main","gitSource_repoId": "e.g. 123456789","gitSource_type": "{{trigger.gitSource_type}}","target": "{{trigger.target}}"}
{"id": "dpl_abc123","url": "my-app-abc123.vercel.app","target": "production","createdAt": 1700000000000,"readyState": "QUEUED"}
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.
Triggered by anything in the catalog. Free tier available. No credit card.