Azure DevOps Make integrationAutomate Azure DevOps with Make.
What happens when your boards and repos start talking to the rest of your stack? The Azure DevOps Make integration gives you 11 modules, including 3 instant triggers. This guide links your organization, then walks you through a first scenario you can test right away.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Azure DevOps Make integration do for you?
The Azure DevOps Make integration lets Make react to what happens in your organization and write back to it. Make builds a scenario, the automation you design as a chain of modules (each module is one brick: a trigger, an action or a search). Azure DevOps can start that chain on its own, and Make can then create, read or update work items.
Turn repository activity into tracked work. Watch Git Events fires as soon as something happens in a repo, and Create a Work Item drops a matching task on the board. Nobody has to retype repo activity into a ticket by hand.
Keep other tools in step with the board. Watch Work Items Events tells Make the moment an event happens on a work item. From there, Get a Work Item pulls its full details so the next module, in another app, receives clean data. If your team tracks requests in a base, the Airtable Make integration is a natural partner.
Tidy up in bulk. Search Work Items returns every item of a given type, or all of them, and Update a Work Item edits each one in turn.
Some limits are worth knowing upfront. The listed modules center on work items; for anything else, Make an API Call reaches the rest of the Azure DevOps API with the same connection. And if you pick too many scopes in a custom app, Make answers with a Requested query string is too long error. The Make troubleshooting guide covers errors like this one.
Azure DevOps may also have a node in n8n. If you are weighing both tools, read n8n vs Make before you commit.
How do you connect Azure DevOps to Make?
- 01
Allow third-party apps in Azure DevOps
Log in to Azure DevOps and open Organization settings > Policies from the left sidebar. Turn on Third-party application access via OAuth. No organization yet? Click Create new organization, give it a name and click Create.
- 02
Copy your organization name
The name sits under Organization Settings. Copy it exactly, spelling included, because the Make connection asks for it in the next step.
- 03
Create the connection in Make
Add any Azure DevOps module to a scenario and click Create a connection. A connection is your account linked to Make once and reused by every module. Paste the name in Organization, click Save, then confirm access if Azure DevOps asks.
Your first scenario with Azure DevOps
GoalWhen a git event happens in an Azure DevOps repository, Make creates a work item so the team can follow it up.
- 01
Create the scenario
On the Scenarios page, create a new scenario and click the big + to add the first module.
- 02
Add the git trigger
Search for Azure DevOps, choose Watch Git Events and pick the connection you created. It is an instant trigger: Azure DevOps calls Make through a webhook as soon as the event happens.
- 03
Set it up
Fill the module fields. Once the connection works, Make lists what it can read in your organization, so you pick from menus instead of typing names from memory.
- 04
Add the work item
Click the + to the right of the trigger and add Create a Work Item. Map data from the git event into the new item so the team can see where it came from.
- 05
Test with Run once
Click Run once, then trigger a real event in the repo. Open each module to read the bundles it received; a bundle is one item passed from a module to the next.
- 06
Switch it on
Happy with the result? Switch the scenario on. From then on, each git event in Azure DevOps reaches Make and turns into a work item.
Triggers that start your Azure DevOps scenarios
3 modules start a scenario when something happens in Azure DevOps. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Azure DevOps as soon as it happens.
Watch Code Events
Instant triggerIn Make“Triggers when an event for code happens.”
Get a scenario started whenever something happens to the code in your Azure DevOps organization. This is the trigger to reach for when the code itself is the signal, and you want the rest of your tools to hear about it without anyone relaying the news.
Watch Git Events
Instant triggerIn Make“Triggers when an event for git happens.”
You hear from Make the moment a git event lands in one of your repositories. It gives a scenario a clean starting point tied to repo activity, which pairs well with Create a Work Item when each event deserves a follow-up task.
Watch Work Items Events
Instant triggerIn Make“Triggers when an event for work items happens.”
Your board becomes a starting line: Make is told when an event happens on a work item, and the scenario takes it from there. Follow it with Get a Work Item when the next step needs the item's full details.
What Make can do in Azure DevOps
Azure DevOps gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a Work Item
ActionIn Make“Creates a new work item.”
A new work item appears on your board without anyone opening Azure DevOps. It is the module that turns a form entry, an email or a git event into something your team will actually track.
Get a Work Item
ActionIn Make“Retrieves details about a specific work item.”
You get the full details of one work item you already know. Choose it over Search Work Items when you hold a single item, for example the one a trigger just handed you, and need everything about it.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
Reach any part of the Azure DevOps API that the other modules leave out, using the connection you already have. It is the fallback when no listed module does what you need.
Update a Work Item
ActionIn Make“Updates a specific work item.”
Change an existing work item from your scenario so the board reflects what happened elsewhere. It saves the round trip of someone reading an update in one tool and retyping it in Azure DevOps.
Search Work Items
SearchIn Make“Searches work items by type or returns them all.”
Pull a set of work items filtered by type, or every item, in one pass. Unlike Get a Work Item, it can return zero, one or many bundles, and each one flows to the next module separately.
Triggers
ActionIn the docs onlyThis entry shows up in the Azure DevOps list in Make under the name Triggers, and neither the directory nor the documentation describes what it does. Open it in the editor and read what it asks for before you rely on it.
Work Items
ActionIn the docs onlyMake lists an entry called Work Items for Azure DevOps, with no official description attached. Rather than guess its behavior, lean on the documented work item modules, which already cover creating, reading, updating and searching items.
Other
ActionIn the docs onlyAn entry named Other sits in the Azure DevOps module list, and Make gives no description of it. Check what it offers inside the editor before building a scenario on it, since this page cannot tell you more.
Need help automating Azure DevOps with Make?
A person reads every message.
