Trigger Build
teamcity.trigger_build
ActionBusiness appsconnection required
Calls the TeamCity API with the connection's credentials.
Queue a build configuration.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- TeamCity
- Secret shape
- the access token, or {"token": "…"}
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 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 |
|---|---|---|---|---|---|
build_type_id Build configuration id. | string | Yes | — | — | — |
branch Name of the branch to act on, as Teamcity spells it. | string | No | — | — | — |
Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}Related TeamCity nodes
See Trigger Build run in a workflow.
In a technical demo we add the TeamCity connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.