create_deployment
Deploy a project using a Git source or inline files. Specify target environment: production, preview, or staging.
Instructions
Create a new deployment. The simplest path is to deploy from a connected Git source: pass name (project) and a gitSource ({ type, repoId/org+repo, ref }). For file-based deploys, provide files. For most workflows the /vercel CLI skill is easier — use this when you need API-driven, headless deploys.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Project name this deployment belongs to. | |
| project | No | Project id (if different from name). | |
| target | No | Deploy target. | |
| gitSource | No | Git source, e.g. { type: 'github', repoId: 123, ref: 'main' } or { type:'github', org, repo, ref }. | |
| files | No | Inline files [{ file, data }] for file-based deploys. | |
| meta | No | Arbitrary metadata key/values. | |
| projectSettings | No | Override project build settings. | |
| teamId | No | Team ID to scope the request. Falls back to VERCEL_TEAM_ID when omitted. | |
| slug | No | Team slug to scope the request (alternative to teamId). |