Vercel Application Deployment
Deploy an approved Git source or file set to Vercel and verify deployment checks.
Works with
name: vercel-application-deployment description: "Deploy an approved Git source or file set to Vercel and verify deployment checks."
Vercel Application Deployment
Deploy an approved Git source or file set to Vercel and verify deployment checks.
Required Aident Actions
- <action-tag>composio:vercel_tools:vercel_get_project2</action-tag> (required inputs: idOrName): Tool to find a project by ID or name with comprehensive details. Use when you need complete project metadata including configuration, deployments, security settings, and analytics.
- <action-tag>composio:vercel_tools:vercel_create_new_deployment</action-tag> (required inputs: name): Tool to create a new deployment. Use when you need to deploy files or a Git commit to a Vercel project.
- <action-tag>composio:vercel_tools:vercel_list_deployment_checks</action-tag> (required inputs: deploymentId): Tool to retrieve a list of checks for a specific deployment. Use after a deployment to inspect check statuses and resultAction · Get Project2on-tag> (required inputs: idOrUrl): Tool to get a deployment by ID or URL. Use when you need to retrieve detailed information about a specific deployment.
Use Aident Loadout to read the current Action schema befoAction · Create New Deployment Vault. If an Action is billable or mutating, run Aident preflight, show the affected target and quoted cost or risk, and wait for eAction · List Deployment Checksuested outcome, source material, destination, audience, constraints, and acceptance criteria. 2. Apply the source-derived guidance below to create a concrete pAction · Get Deployment Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default. 4. Inspect the current schema and prepare the minimum valid input for each selected Action. 5. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps. 6. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.
Source-Derived Guidance
- Confirm project, source revision, and preview or production target.
- Capture the deployment ID and verify every returned check before reporting success.
Execution Boundaries
- Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
- Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
- Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
- Read current state before a mutation, state the exact target, and include a rollback or recovery step in the result.
- After Vercel accepts a deployment, pass its returned ID to composio:vercel_tools:vercel_get_deployment at moderate intervals until READY or a terminal failure. Do not report the deployment as successful while it is queued or building.
- Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.
Output
Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.
Attribution
This Skill adapts the reviewed upstream workflow. See for the pinned source and for the preserved license.