Build definition to trigger on.

The project to create the service hook subscription in. You must either be an administrator of this project or have the required permissions.

The project to create the service hook subscription in. You must either be an administrator of this project or have the required permissions.

The project to create the service hook subscription in. You must either be an administrator of this project or have the required permissions.

Project containing the build definition.

Build definition to trigger a new build on.

Must be a project administrator for the specified project in order to create a Zap.

A specific work item number (for example, "123") or a string containing a work item number in the format "#123" (for example, "Link to #123 please").

URL of the link to be added to the work item.

Comment for the link. This comment is associated with the link, and is not added as a comment on the work item itself.

The project to create the service hook subscription in. You must either be an administrator of this project or have the required permissions.

Filter to checkins that change one or more files under the specified path (it should start with $/[Project]).

String that must be found within the comment.

The project to create the service hook subscription in. You must either be an administrator of this project or have the required permissions.

Only trigger if this field was changed by the update to the work item.

The project to create the service hook subscription in. You must either be an administrator of this project or have the required permissions.

The project where work item will be created.

Work item type.

Work item title.

The area of the product with which this work item is associated.

The iteration within which this work item will be associated.

The person currently owning the work item.

Work item description.

API docs for Azure DevOps are located here https://www.visualstudio.com/en-us/integrate/api/overview

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, {"foo": "bar"} is perfectly valid.