Appearance
Vercel
Manage deployments, projects, and domains on the Vercel platform.
| Detail | Value |
|---|---|
| Category | Cloud & Infra |
| Base URL | https://api.vercel.com |
| Authentication | Bearer Token |
| Endpoints | 5 |
| Connector key | vercel |
Using Vercel in a workflow
- Go to Connections and click New Connection.
- Pick Vercel from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /v9/projects | List all projects |
GET /v9/projects/{idOrName} | Get a project |
GET /v6/deployments | List deployments |
GET /v5/domains | List domains |
GET /v2/teams | List teams |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /v9/projects
List all projects
| Detail | Value |
|---|---|
| Operation ID | hosting.listProjects |
| Method | GET |
| Path | /v9/projects |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
limit | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Vercel connection from the Connection dropdown.
- In the Operation dropdown, select
hosting.listProjects. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Vercel API reference.
GET /v9/projects/{idOrName}
Get a project
| Detail | Value |
|---|---|
| Operation ID | hosting.getProject |
| Method | GET |
| Path | /v9/projects/{idOrName} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
idOrName | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Vercel connection from the Connection dropdown.
- In the Operation dropdown, select
hosting.getProject. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Vercel API reference.
GET /v6/deployments
List deployments
| Detail | Value |
|---|---|
| Operation ID | hosting.listDeployments |
| Method | GET |
| Path | /v6/deployments |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
projectId | query | string | No |
limit | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Vercel connection from the Connection dropdown.
- In the Operation dropdown, select
hosting.listDeployments. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Vercel API reference.
GET /v5/domains
List domains
| Detail | Value |
|---|---|
| Operation ID | hosting.listDomains |
| Method | GET |
| Path | /v5/domains |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
limit | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Vercel connection from the Connection dropdown.
- In the Operation dropdown, select
hosting.listDomains. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Vercel API reference.
GET /v2/teams
List teams
| Detail | Value |
|---|---|
| Operation ID | hosting.listTeams |
| Method | GET |
| Path | /v2/teams |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Vercel connection from the Connection dropdown.
- In the Operation dropdown, select
hosting.listTeams. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Vercel API reference.