Skip to content

Automate Azure DevOps

Keep track of pull requests, pipeline runs and work items in Azure DevOps without refreshing boards all day. New PRs and failed builds reach your team as they happen, and each person gets the work items assigned to them. Describe what you want to your AI assistant, check what it will do, and it keeps running with your laptop closed.

Try asking

Create a ClickRuntime automation: whenever a pull request is created in our Azure DevOps repo web-app, post the title, author and link to #code-review in Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Build your own

Build any Azure DevOps automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Azure DevOps should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every morning, list Azure DevOps work items in the current sprint that are still New with less than three days left.

When an Azure DevOps build fails on main, post the pipeline name, commit and error in Slack.

Each Friday, gather closed Azure DevOps work items, have AI write release notes, save them to Confluence and send a Microsoft Teams message.

Beyond chat

Have Azure DevOps work when you're not in the chat

Connecting Azure DevOps to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Azure DevOps

You connect Azure DevOps with a personal access token you create yourself, limited to one organization and the scopes you pick.

Azure DevOps

DevOps / Project management

  1. In Azure DevOps, open User settings (top right) and choose Personal access tokens.
  2. Select + New Token, then choose the organization and an expiry date.
  3. Add the scopes the automation needs, such as Work Items Read & Write, Code Read or Build Read & Execute.
  4. Copy the token. Azure DevOps only shows it once.
  5. In the ClickRuntime dashboard, open Connections & secrets and save the token as a secret for Azure DevOps.

Good to know

Azure DevOps limits that affect automations

  • The token works in the one organization you chose when creating it, and only for its scopes.
  • Your organization's admins can set a maximum token lifetime, which limits the expiry you can pick. When the token expires, create a new one and update the secret.
  • In organizations backed by Microsoft Entra, a token that goes unused for 90 days becomes inactive.
  • Instant alerts for new pull requests or finished builds use a service hook that you add in your project settings, pointing at the automation's link.

FAQ

Questions about automating Azure DevOps

What can ClickRuntime see in Azure DevOps?
Only what your personal access token allows, in the organization it was created for. With Work Items Read it can query and read work items, with Code Read it can see pull requests, and with Build Read it can check pipeline runs.
How do alerts arrive the moment something happens?
You add a service hook in your Azure DevOps project settings, for example for pull request created or build completed, and point it at the link the automation gives you. Each event is handled as it arrives.
What happens when my token expires?
Requests start failing. Create a new token with the same scopes in User settings and replace the secret in Connections & secrets. Pick an expiry that fits your organization's policy.
Can it change work items?
Only if your token has a write scope such as Work Items Read & Write. With read scopes alone it can list and report, but not edit.
Do I need AI for Azure DevOps automations?
No. Pull request alerts, build failure alerts and work item emails run without it. If you want summaries or triage, they use the AI that comes with every ClickRuntime plan, so you don't need your own AI key.
Is this a Azure DevOps connector for ChatGPT or Claude?
Not for chatting with Azure DevOps data. A chat connector lets your assistant read and change Azure DevOps while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Azure DevOps event.

Tell your assistant what Azure DevOps should do

Free plan. No credit card.