Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Release Product → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Release Product resource with the Post Undefined operation, it sends a POST request with a complex JSON body to create or update release product data in Halo PSA.

Typical use cases include automating the synchronization of release-related information such as emails, components, project details, mappings for DevOps and Jira fields, branches, and filters. This is useful for teams managing software releases who want to automate updates between Halo PSA and their DevOps or Jira environments.

For example, you might use this node to programmatically post a new release product configuration that includes mappings from Jira ticket statuses to Halo PSA statuses, or to define which branches and components are part of a release.

Properties

Name Meaning
Body A JSON object representing the release product data to send. It includes nested structures such as:
- release_emails: List of email objects related to the release.
- components: List of component objects.
- devops_project: Object describing the DevOps project.
- devops_otherfield_mappings: Array of other field mappings for DevOps.
- devops_instance: Object containing multiple mapping arrays (fields to sync, status, priority, area path, iteration path, other fields), filters, and import entities list.
- branches: List of branch objects.
- jira_instance: Object with Jira-specific mappings (status, ticket type, Jira fields, priority).
- jirafield_mappings: Array of Jira field mappings.
- jira_project: Object describing the Jira project.

The property expects a valid JSON structure matching the API schema for release products.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains:

  • json: The parsed JSON response returned by the Halo PSA API after posting the release product data.
  • pairedItem: Metadata linking the output to the input item index.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Halo PSA API.
  • The node uses credentials including base URL, tenant identifier, client ID, and client secret to authorize requests.
  • No additional external dependencies beyond the Halo PSA API and n8n's HTTP request helper.

Troubleshooting

  • No credentials returned!
    This error occurs if the required API authentication credentials are not configured or accessible. Ensure that the API key credential is properly set up in n8n.

  • Resource or Operation not found
    If the specified resource or operation does not exist in the node's configuration, verify that "Release Product" and "Post Undefined" are correctly selected.

  • Invalid JSON in Body property
    Since the body is expected as JSON, malformed JSON will cause parsing errors. Use a JSON validator to ensure correctness before running the node.

  • API request failures
    Network issues, invalid credentials, or incorrect request body structure can cause API errors. Check the error message returned in the output JSON for details. Enabling "Continue On Fail" allows processing subsequent items even if some fail.

Links and References

Discussion