Run Pipeline
azure_devops.run_pipeline
ActionMicrosoft Azureconnection required
Calls the Azure DevOps API with the connection's credentials.
Queue a pipeline run.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Azure DevOps
- Secret shape
- the PAT, or {"token": "…"}
- Config it needs
- organization, project
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
pipeline_id Id of the pipeline to act on, from azure_devops.list_pipelines — not its name. | string | Yes | — | — | — |
branch Branch name (main) or a full ref (refs/tags/v1.2.0, refs/pull/42/merge). | string | No | — | — | — |
variables Pipeline variables, e.g. {"env": "staging"}. | object | No | — | — | {"env":"staging"} |
template_parameters Template parameters, for a YAML pipeline that declares them. | object | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"variables": {
"env": "staging"
}
}Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}See Run Pipeline run in a workflow.
In a technical demo we add the Azure DevOps connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.