Appearance
Azure DevOps
Manage projects, repos, pipelines, builds, and work items in Azure DevOps.
| Detail | Value |
|---|---|
| Category | DevOps |
| Base URL | https://dev.azure.com/{organization} |
| Authentication | API Key |
| Endpoints | 8 |
| Connector key | azure-devops |
Using Azure DevOps in a workflow
- Go to Connections and click New Connection.
- Pick Azure DevOps 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 /_apis/projects | List projects |
POST /_apis/projects | Create a project |
GET /{project}/_apis/git/repositories | List repositories |
GET /{project}/_apis/pipelines | List pipelines |
POST /{project}/_apis/pipelines/{pipelineId}/runs | Run a pipeline |
GET /{project}/_apis/build/builds | List builds |
GET /{project}/_apis/wit/workitems/{id} | Get a work item |
GET /{project}/_apis/git/repositories/{repositoryId}/pullrequests | List pull requests |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /_apis/projects
List projects
| Detail | Value |
|---|---|
| Operation ID | devops.listProjects |
| Method | GET |
| Path | /_apis/projects |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure DevOps connection from the Connection dropdown.
- In the Operation dropdown, select
devops.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 Azure DevOps API reference.
POST /_apis/projects
Create a project
| Detail | Value |
|---|---|
| Operation ID | devops.createProject |
| Method | POST |
| Path | /_apis/projects |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure DevOps connection from the Connection dropdown.
- In the Operation dropdown, select
devops.createProject. - 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 Azure DevOps API reference.
GET /{project}/_apis/git/repositories
List repositories
| Detail | Value |
|---|---|
| Operation ID | devops.listRepositories |
| Method | GET |
| Path | /{project}/_apis/git/repositories |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure DevOps connection from the Connection dropdown.
- In the Operation dropdown, select
devops.listRepositories. - 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 Azure DevOps API reference.
GET /{project}/_apis/pipelines
List pipelines
| Detail | Value |
|---|---|
| Operation ID | devops.listPipelines |
| Method | GET |
| Path | /{project}/_apis/pipelines |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure DevOps connection from the Connection dropdown.
- In the Operation dropdown, select
devops.listPipelines. - 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 Azure DevOps API reference.
POST /{project}/_apis/pipelines/{pipelineId}/runs
Run a pipeline
| Detail | Value |
|---|---|
| Operation ID | devops.runPipeline |
| Method | POST |
| Path | /{project}/_apis/pipelines/{pipelineId}/runs |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure DevOps connection from the Connection dropdown.
- In the Operation dropdown, select
devops.runPipeline. - 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 Azure DevOps API reference.
GET /{project}/_apis/build/builds
List builds
| Detail | Value |
|---|---|
| Operation ID | devops.listBuilds |
| Method | GET |
| Path | /{project}/_apis/build/builds |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure DevOps connection from the Connection dropdown.
- In the Operation dropdown, select
devops.listBuilds. - 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 Azure DevOps API reference.
GET /{project}/_apis/wit/workitems/{id}
Get a work item
| Detail | Value |
|---|---|
| Operation ID | devops.getWorkItem |
| Method | GET |
| Path | /{project}/_apis/wit/workitems/{id} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure DevOps connection from the Connection dropdown.
- In the Operation dropdown, select
devops.getWorkItem. - 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 Azure DevOps API reference.
GET /{project}/_apis/git/repositories/{repositoryId}/pullrequests
List pull requests
| Detail | Value |
|---|---|
| Operation ID | devops.listPullRequests |
| Method | GET |
| Path | /{project}/_apis/git/repositories/{repositoryId}/pullrequests |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Azure DevOps connection from the Connection dropdown.
- In the Operation dropdown, select
devops.listPullRequests. - 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 Azure DevOps API reference.