TeamCity

Business appsBearer tokenConnection test available

Queue and monitor TeamCity builds.

OCNORA ships 3 typed TeamCity operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.

Before you connect TeamCity

Authentication
Bearer token
Credential
the access token, or {"token": "…"}
Connection test
Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.

What you can do with TeamCity

Operations, grouped by what they do to your data.

Create and send 1

Read and search 2

A sample TeamCity workflow

  1. 1
    A core trigger
    Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no TeamCity trigger is needed.
  2. 2
    Get Buildteamcity.get_build
    Fetch one build by id.
  3. 3
    Trigger Buildteamcity.trigger_build
    Queue a build configuration.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.

TeamCity questions

How does OCNORA authenticate with TeamCity?
With a stored Bearer token credential, shaped the access token, or {"token": "…"}. A connection test can check it when you add it.
What can I automate with TeamCity?
3 typed operations, each with a reference page listing its config fields and the shapes it emits.
What if the TeamCity operation I need is not listed?
Where TeamCity has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use TeamCity?
Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are TeamCity calls controlled?
Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first TeamCity workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.