Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Azure Dev Ops → Post Undefined

AI-generated

Overview

This node integrates with the Azure DevOps API to perform a custom POST operation labeled "Post Undefined" under the "Azure Dev Ops" resource. It allows users to send complex JSON payloads directly to a specified endpoint in Azure DevOps, enabling advanced or less common API interactions that may not be covered by predefined operations.

Typical use cases include synchronizing fields, mapping statuses, priorities, area paths, iteration paths, and other custom fields between systems, applying filters, or importing entities based on user-defined JSON structures. This flexibility is useful when automating complex workflows involving Azure DevOps work items or configurations that require detailed customization.

For example, a user might configure this node to post a JSON body defining how different work item fields should synchronize between Azure DevOps and another system, or to import specific entities with customized mappings.

Properties

Name Meaning
Body A JSON object representing the request payload to send in the POST operation. It supports complex nested structures including lists for fields to sync, status mappings, priority mappings, area path mappings, iteration path mappings, other field mappings, filters, and import entities. The default value is a template JSON illustrating these sections.

The "Body" property expects a valid JSON string which will be parsed and sent as the HTTP request body.

Output

  • The node outputs an array of JSON objects corresponding to each input item processed.
  • Each output item contains a json field holding the response from the Azure DevOps API after performing the POST request.
  • If the request fails and "Continue On Fail" is enabled, the output will contain an error message inside the json.error field.
  • No binary data output is produced by this node.

Dependencies

  • Requires an API authentication credential for Azure DevOps (an API key or token) configured in n8n credentials.
  • The node uses the base URL, tenant ID, client ID, and client secret from the credentials to authenticate requests.
  • The node depends on n8n's HTTP request helper methods to perform the API call.
  • No additional external libraries beyond those bundled with n8n are required.

Troubleshooting

  • Common Issues:

    • Invalid JSON in the "Body" property will cause parsing errors before sending the request.
    • Missing or incorrect API credentials will result in authentication failures.
    • Incorrect or unsupported JSON structure may lead to API errors from Azure DevOps.
    • Network connectivity issues can prevent successful API calls.

  • Error Messages:

    • "No credentials returned!": Indicates missing or misconfigured Azure DevOps API credentials.
    • Errors returned from the Azure DevOps API will be included in the output if "Continue On Fail" is enabled; otherwise, they will stop execution.
    • JSON parsing errors if the "Body" property contains invalid JSON syntax.

  • Resolution Tips:

    • Validate the JSON syntax in the "Body" property before running the node.
    • Ensure the Azure DevOps API credentials are correctly set up and have sufficient permissions.
    • Review the Azure DevOps API documentation to confirm the expected structure of the POST payload.
    • Enable "Continue On Fail" during testing to capture error details without stopping the workflow.

Links and References

Discussion