Integrations / TeamCity

TeamCity notifications in Microsoft Teams

TeamCity build results in Teams — via a native webhook or the tcWebHooks plugin. Per My Last Webhook normalizes TeamCity events into rich Adaptive Cards and posts them to a Teams channel, a person's DM, or a webhook — the successor to Office 365 Connectors.

How it works

  1. TeamCity POSTs a webhook to your private ingest URL when a build runs.
  2. We normalize it — the same card format as every other platform.
  3. The card lands in your chosen Teams destination, with routing and noise controls applied.

Set up in minutes

Create a subscription in the app (platform: TeamCity), copy its ingest URL, then:

1

Create a subscription (platform TeamCity) and copy its ingest URL.

2

In TeamCity, add a webhook (native build feature, or the tcWebHooks plugin) pointing at the ingest URL.

3

Use a JSON template that posts the build name, number, result, branch, and commit (see the reference).

4

Run a build → the card lands.

See it instantly

Don't want to wait for a build? Hit Test on the subscription — a card lands immediately. Full steps in the platform reference.

What lands in Teams

Teams · #ci
🔴 Widgets :: Build · failure
TeamCity · main · alice · 3m 20s

Built for teams, not just alerts

Routing PRO

Prod failures to #prod-alerts, the rest to #ci.

Incident mode PRO

Collapse a flapping pipeline into one updating card.

On-call DMs PRO

DM the owner the moment their TeamCity build breaks.

Status filters

Only care about failures? Filter to just those — free.

Part of Per My Last Webhook — all 17 integrations into one Teams app.

▣ StartPER MY LAST WEBHOOKC:\INTEGRATIONS\TEAMCITYStatus: 200 OK