Azure DevOps AdvancedInstall

Summary

Lists pull requests in an Azure DevOps Git repository, optionally filtered by status, creator, reviewer, source/target branch, and a result limit. Each returned pull request becomes its own output item.

Inputs

• project (required) — Azure DevOps project name or ID that contains the repository.
• repositoryId (required) — Repository ID or name to list pull requests from.
• listOptions.status — Filter by PR status: active, abandoned, all, completed, or notSet. Defaults to active when the option is added. It is sent as searchCriteria.status.
• listOptions.creatorId — Only PRs created by this identity ID (searchCriteria.creatorId).
• listOptions.reviewerId — Only PRs where this identity ID is a reviewer (searchCriteria.reviewerId).
• listOptions.sourceRefName — Only PRs from this source branch, e.g. refs/heads/my-feature (searchCriteria.sourceRefName).
• listOptions.targetRefName — Only PRs into this target branch, e.g. refs/heads/main (searchCriteria.targetRefName).
• listOptions.top — Maximum number of PRs to return ($top). Defaults to 100 when the option is added.

Output shape

One output item per pull request, taken from the value array of the Azure DevOps response. Each item holds the raw pull request JSON.

If the List Options collection is left empty, no status filter is sent, so Azure DevOps applies its own default (normally active PRs). No pagination is implemented, so use Top to cap results. Filter values are appended to the URL without encoding. Ref names containing special characters may need care. With Continue On Fail enabled, errors are returned as an item with an error message.

Examples

Example 1: Fetch all open PRs targeting main for a daily review digest.

Project: MyProject; Repository: my-repo; List Options: Status=Active, Target Ref Name=refs/heads/main.

Example 2: Find all completed PRs from a specific author.

Project and Repository set; List Options: Status=Completed, Creator ID=, Top=50.

Links

• n8n community nodes installation guide