Resources · Zapier integration

Azure DevOps Zapier integrationAutomate Azure DevOps with Zapier.

The Azure DevOps Zapier integration gives you 6 triggers, 5 actions and 1 search. The triggers follow builds, code and work items, and all 6 are instant on every plan. Most of them ask for project admin rights first, so check those before building.

See the 12 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Azure DevOps Zapier integration actually does

Azure DevOps is where software teams plan work, host code and run builds in the cloud. The Azure DevOps Zapier integration lets Zapier listen to those projects and act on them: a Zap (the automation you build in Zapier) starts on a push, a finished build or a work item, then creates, updates or links work items, or queues a build.

Three results teams build first. Builds that start themselves: Code Push (Git) fires when code reaches a repository, and Trigger Build queues the build definition you choose. A ticket after the builds that matter: Completed Build fires when a build ends, a filter keeps the ones that match your rule, and Create Work Item files a ticket. Comments that move work: New Work Item Comment only fires when a comment contains the text you set, and Update Work Item changes the item accordingly.

What Zapier does not do here: it does not let anyone set up triggers without the right permissions. Every trigger creates a service hook subscription in a project, so the connected account must be a project administrator or hold the required permissions. Zapier also never replays history: pushes, builds and items from before the Zap was published are not picked up.

If you are comparing tools, the same breakdown exists for the Azure DevOps Make integration, and our n8n vs Zapier comparison puts the two tools next to each other.

Vocabulary

Zapier in one minute

Eight words you will see in the editor. Each one is explained once, here, then used as is.

Zap
The automation itself: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something on your behalf.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan allowance is counted in tasks.
Instant vs polling
An instant trigger is reported by the app as it happens. A polling one is checked on a timer. All Azure DevOps triggers are instant.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and quietly stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Connection
Your Azure DevOps account, linked to Zapier once and then reused by every Azure DevOps step in every Zap.
Cost

What it really costs

Zapier bills tasks, and only completed actions count. Pushes, builds and comments that start a Zap are free.

  • TriggerNever costs a task
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps only
  • Premium appNo, Azure DevOps works on the free plan

Azure DevOps is not a premium app, so it runs on the free plan: 100 tasks a month and unlimited Zaps. The free plan stops at two steps, though, one trigger and one action. A filter, a second action or the Find Work Item search makes a multi-step Zap, which needs a paid plan. A failed action is not counted. The polling grid below does not apply: every Azure DevOps trigger is instant, whatever your plan.

Connect

Connect your Azure DevOps account

  1. 01

    Find Azure DevOps in Apps

    In your Zapier account, open Apps and click + Add connection. Type Azure DevOps in the search box and select it. You do this once; every Zap can then use the connection.

  2. 02

    Sign in to Azure DevOps

    Click Add connection and sign in to Azure DevOps in the new tab. Use the account that administers the projects your Zaps will watch, or one that holds the required permissions on them.

  3. 03

    Grant access

    Accept the access request so Zapier can read your projects and write work items or queue builds. From then on, every Azure DevOps step reuses this connection without asking you to sign in again.

First Zap

Your first Azure DevOps Zap, step by step

GoalA small product team wants a fresh build queued whenever someone pushes code that meets their rule, without opening the pipeline page.

  1. 01

    Build the trigger

    Create a Zap and choose Azure DevOps with Code Push (Git). Pick the Project; the account must be its administrator or hold the required permissions.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent pushes from that project, so you set up the next steps on a real push, not on a guess.

  3. 03

    Add the filter

    Add a Filter step and set the field to read, the rule and the value. A text rule only works on text, a number rule only on numbers; the wrong type never passes.

  4. 04

    Queue the build

    Add Azure DevOps with Trigger Build. Choose the Project that holds the build definition, then the Build Definition itself. Test the step and check the build appears.

  5. 05

    Publish

    Click Publish to switch the Zap on. With the filter, this is a three-step Zap that needs a paid plan. On the free plan, drop the filter and queue a build on every push.

Triggers

Azure DevOps triggers

6 events start a Zap when something happens in Azure DevOps, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Completed Build

Instant trigger

In Zapier“Triggers when a build completes.”

Starts the Zap when a build of the definition you pick completes. It is the signal to hang everything that should follow a build: alerts, tickets, the next step of a release.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a broken build of the main product should land as a bug in the backlog before the team arrives.
Watch out
both Build Definition and Project are required, and the project needs admin rights or the required permissions for the subscription.
2

Code Check-In (TFVC)

Instant trigger

In Zapier“Triggers when code is checked into Team Foundation version control.”

Reacts to code checked into Team Foundation version control (TFVC). Teams that work in TFVC get the same instant signal Git teams get from a push.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a check-in under the release folder of a legacy product should alert the person who signs off releases.
Watch out
Path is required and must start with $/[Project]. Only check-ins that change files under that path start the Zap.
3

Code Push (Git)

Instant trigger

In Zapier“Triggers when code is committed and pushed to a Git repository on Visual Studio Team Services.”

Fires when code is committed and pushed to a Git repository in your project. For Git teams, this is the most direct link between a developer's work and anything that should follow it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every push should queue a build, so nobody forgets to start one by hand.
Watch out
Project is required, and the subscription needs admin rights or the required permissions on it.
4

New Work Item Comment

Instant trigger

In Zapier“Triggers when a work item is commented on.”

A comment on a work item becomes the starting signal, but only if the comment contains the text you set. It turns a plain comment into a command your team can type.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
writing a set keyword in a comment should flag the item for the support lead.
Watch out
Contains String is required, so a Zap cannot listen to every comment. Pick a word nobody types by accident.
5

New Work Item

Instant trigger

In Zapier“Triggers when a work item is created.”

Fires once for each work item created in the project you choose, whatever its type. It is the clean entry point when every new bug, task or story deserves a reaction.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
each new item should get a link to the team's triage guide attached straight away.
Watch out
if another Zap creates work items in the same project, this one will start on them too. Plan for that loop.
6

Updated Work Item

Instant trigger

In Zapier“Triggers when a work item is updated.”

Reacts each time a work item in the project is updated, whatever changed. A busy item can therefore start the Zap many times in a single day.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a change to an item should queue a build with Trigger Build, behind a filter on the field that matters.
Watch out
never pair it with Create Work Item: you would get a new item on every update. Any step that writes back to the same item, such as Update Work Item or Add Link to Work Item, can set it off again.
Actions

Azure DevOps actions

Azure DevOps gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Trigger Build

Action

In Zapier“Queues a new build.”

Queues a new build of the definition you choose.

When to use it
a comment keyword or a new work item should start a build without anyone clicking Run.
Watch out
Project and Build Definition are both required. A Zap that queues builds from Completed Build on the same definition will loop.
2

Create Work Item

Action

In Zapier“Create a new work item.”

Files a new work item in the project you pick, with its type and title.

When to use it
a failed build or an outside request should end up as a ticket the team can plan.
Watch out
Project, Type and Title are all required. Map the title from the trigger so items are not all named the same.
3

Update Work Item

Action

In Zapier“Updates a Work Item in Azure DevOps”

Changes an existing work item, identified by its ID, and lets you mute notifications for that change.

When to use it
a keyword in a comment should move or reassign the item without anyone opening it.
Watch out
Work Item takes an ID; when the trigger does not carry it, put Find Work Item before this step.
5

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced action that sends your own request to Azure DevOps, already signed in with your connection.

When to use it
what you need is not covered by the other four actions and someone on the team knows the Azure DevOps API.
Watch out
it only reaches domains tied to Azure DevOps, and Stop on error decides whether a failure halts the Zap.
Searches

Azure DevOps search

1 search step looks for data that already exists in Azure DevOps, so a later step can use it.

A search step reads what already exists instead of creating it. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not what you expected.

1

Find Work Item

SearchFind or create

In Zapier“Find Work Item using the query ID or Work Item Query Language (WIQL) syntax”

Finds work items with a saved query or a query written in WIQL, the Work Item Query Language, then hands the result to later steps.

When to use it
an Update Work Item step needs an ID the trigger did not carry.
Watch out
Project and Team are required. The editor also shows Find or Create Work Item: same search, create box ticked.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that depend on it. Switched on, the Zap carries on empty-handed.
  2. Create Work Item if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: it asks for the fields needed to create the missing item, and the setting above disappears.
  3. If multiple search results are found?
    Keep the first match, which is the default, stop the Zap, or pass every match on to the next steps at once.
When it breaks

When an Azure DevOps Zap breaks

Zapier attaches no help article to Azure DevOps. The cases below combine Zapier's general limits with the permission rules stated in the operations themselves.

None of them raises an alert. A Zap can look healthy while it queues builds in a loop or files duplicate tickets. When something looks off, our Zapier troubleshooting page lists the checks to run.

  • No admin rights, no trigger

    Each trigger creates a service hook subscription in the project. Without admin rights or the required permissions, the trigger cannot be set up.

  • Build loops

    Completed Build feeding Trigger Build on the same definition starts a new build every time one finishes, and burns through your tasks fast.

  • Duplicates from updates

    Updated Work Item fires on every change. Creating an item from it makes one new ticket per update, not one per source item.

  • No catch-up on history

    A Zap only reacts to what happens after you publish it. Older pushes, builds and work items are never picked up; moving them is a separate job.

  • Bulk imports held back

    Importing many work items at once can send Zapier a sudden flood of events. Its flood protection may hold that batch back instead of running it.

  • A comment Zap that stays silent

    New Work Item Comment only fires when the comment contains your Contains String. A typo in that text means the Zap never starts.
Need help

Need help automating Azure DevOps with Zapier?

A person reads every message.

FAQ

Azure DevOps Zapier integration: questions

01Is the Azure DevOps Zapier integration free?
Yes, on the Zapier side. Azure DevOps is not a premium app, so it works on the free Zapier plan, which gives you 100 tasks a month and unlimited Zaps. The catch is the shape: a free Zap has two steps, one trigger and one action. A filter, the Find Work Item search or a second action make it a multi-step Zap, and those need a paid plan. Sketch your Zap first to see which plan it really needs.
02How many tasks does an Azure DevOps Zap use?
One per action that completes. Triggers never count, so a push, a build or a comment that starts a Zap costs nothing by itself. A Zap that queues one build uses one task each time it runs; one that also files a work item uses two. A failed action is not counted against your plan. If a filter stops the Zap, the actions after it do not run and cost nothing. Loops are the real risk, since a build that starts a build can run all day.
03Does it work in real time?
Yes. All six Azure DevOps triggers are instant: Azure DevOps tells Zapier the moment a build completes, code is pushed or checked in, or a work item is created, updated or commented on. The Zap starts right away, whatever your plan. The polling interval grid, 15 minutes on the free plan, does not apply to any of them. In the editor, a Zap built on one of these triggers shows a lightning bolt.
04What does it take to connect Azure DevOps to Zapier?
An Azure DevOps account with the right rights on the project. Every trigger creates a service hook subscription in the project you pick, so the account must be a project administrator or hold the required permissions. Add Link to Work Item also requires project admin rights. You connect once from the Apps page of Zapier with + Add connection, sign in to Azure DevOps and accept the access request. Every step then reuses that one connection.
05Why can a trigger not be set up on a project?
Check permissions first. Each Azure DevOps trigger works by creating a service hook subscription inside the project you choose, and only a project administrator, or an account with the required permissions, can do that. The fix sits in Azure DevOps, not in Zapier: grant the rights to the connected account, or reconnect with an account that has them. Then build the trigger again and run the test. No other setting is involved.
06What if the Azure DevOps action you need is not in Zapier?
Then the regular actions cannot do it, and there is one fallback. The four standard actions create, update and link work items and queue builds, and the search finds work items. Beyond that, API Request (Beta) sends a request of your own to Azure DevOps with your connection already signed in. It suits a team that knows the Azure DevOps API. Otherwise, check what the Azure DevOps Make integration offers.
07Zapier, Make or n8n for Azure DevOps?
It depends on your criteria, not on a ranking. Compare three things: which Azure DevOps operations each tool exposes, how each one bills a run, and who on your team will maintain the automation. On Zapier the facts are on this page: six instant triggers, five actions including an advanced API request, one search, one task per successful action and two-step Zaps on the free plan. Ask the other tools the same questions before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations