Skip to content
Azure DevOps logoCloudConvert logo

Connect Azure DevOps to CloudConvert

Move data between Azure DevOps and CloudConvert 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
CloudConvert triggers
3
CloudConvert actions
7

Automation ideas

What you can build with Azure DevOps and CloudConvert

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

  • New or Updated Work Item (Instant) in Azure DevOps creates Convert File in CloudConvert

    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 Job Event in CloudConvert creates Create Work Item in Azure DevOps

    Triggers when a new job has been created

  • New or Updated Work Item (Instant) in Azure DevOps creates Capture Website in CloudConvert

    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 Job Event in CloudConvert creates Get Work Item in Azure DevOps

    Triggers when a new job has been created

  • New or Updated Work Item (Instant) in Azure DevOps creates Merge Files to PDF in CloudConvert

    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 Job Event in CloudConvert creates Update Work Item in Azure DevOps

    Triggers when a new job has been created

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 CloudConvert, 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.