Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Feedback → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Feedback resource with the Post Undefined operation, it allows users to send complex JSON payloads representing feedback data to the Halo PSA system.

Typical use cases include automating the submission of detailed customer feedback or survey results into Halo PSA from other systems or workflows. For example, a company could collect survey responses via a form and then use this node to post that structured feedback directly into their PSA platform for further processing or analysis.

Properties

Name Meaning
Body A JSON object representing the feedback data to be posted. This includes nested structures such as custom survey fields, validation data, visibility conditions, access control settings, translations, and more. The property expects a full JSON payload describing the feedback details according to the Halo PSA API schema.

The "Body" property is designed to accept a rich JSON structure, allowing detailed customization of the feedback content sent to the API.

Output

  • The node outputs an array of JSON objects corresponding to each input item processed.
  • Each output item contains a json field with the response returned by the Halo PSA API after posting the feedback.
  • If the request fails and "Continue On Fail" is enabled, the output will contain an error message in the json.error field.
  • The node does not output binary data.

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 capabilities.

Troubleshooting

  • No credentials returned!: This error occurs if the node cannot retrieve the required API authentication credentials. Ensure that valid credentials are configured in n8n before running the node.
  • Resource or Operation not found: Indicates that the specified resource or operation name does not match those defined in the node. Verify that "Feedback" is selected as the resource and "Post Undefined" as the operation.
  • JSON parsing errors: Since the "Body" property expects a JSON string, malformed JSON will cause errors. Use proper JSON formatting and validate the JSON before input.
  • API request failures: Network issues, invalid credentials, or incorrect payload structure can cause the API call to fail. Check the error messages returned in the output and verify API access and payload correctness.
  • Enable "Continue On Fail" to allow the workflow to proceed even if some items fail, capturing error details in the output.

Links and References

Discussion