Skip to content
Azure DevOps logoDigitalOcean logo

Connect Azure DevOps to DigitalOcean

Move data between Azure DevOps and DigitalOcean the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Azure DevOps triggers
2
Azure DevOps actions
6
DigitalOcean triggers
0
DigitalOcean actions
11

Automation ideas

What you can build with Azure DevOps and DigitalOcean

A few flows teams run between Azure DevOps and DigitalOcean. Use one as a starting point, or build your own from scratch.

  • New or Updated Work Item (Instant) in Azure DevOps creates List All Domains in DigitalOcean

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New or Updated Work Item (Instant) in Azure DevOps creates Create Domain in DigitalOcean

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New or Updated Work Item (Instant) in Azure DevOps creates Get Domain in DigitalOcean

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New or Updated Work Item (Polling) in Azure DevOps creates List All Domains in DigitalOcean

    Polls Azure DevOps every few minutes and fires when a work item is created or updated. Use this when your Activepieces instance is not reachable from the public internet; otherwise prefer the Instant trigger. Pick a work item type to unlock the state filter.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Azure DevOps and acts in DigitalOcean, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.