Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Costcentres → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Costcentres resource with the Post Undefined operation, it allows sending a custom JSON body in the request to create or update cost centre data (or perform other POST-related actions as defined by the API). This flexibility is useful when you want to send arbitrary JSON payloads directly to the API endpoint related to cost centres without predefined fields.

Common scenarios include:

  • Creating new cost centres with custom attributes.
  • Sending updates or commands that require a JSON body not covered by standard operations.
  • Integrating complex or evolving API features where the exact request body structure may vary.

Example: You might use this node to post a JSON object defining a new cost centre with specific properties like name, code, and description, depending on what the Halo PSA API expects.

Properties

Name Meaning
Body A JSON object representing the request body to be sent with the POST request. This allows full customization of the data sent to the Costcentres endpoint.

Output

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

  • json: The parsed JSON response from the Halo PSA API after performing the POST request on the Costcentres resource. This typically includes details about the created or updated cost centre or any response data returned by the API.

If the API returns binary data (not typical for this operation), it would be included in the binary output, but this operation primarily deals with JSON data.

Dependencies

  • Requires valid credentials for the Halo PSA API, including base URL, tenant identifier, client ID, and client secret.
  • The node uses these credentials to authenticate requests via HTTP headers.
  • 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 credentials. Ensure that the API key credential is properly configured in n8n.

  • Resource or Operation not found
    If the specified resource or operation does not exist, verify that "Costcentres" and "Post Undefined" are correctly selected.

  • Invalid JSON in Body property
    Since the Body property expects a JSON object, malformed JSON will cause parsing errors. Make sure the JSON syntax is correct.

  • API request failures
    Errors returned from the Halo PSA API (e.g., authentication failure, validation errors) will appear in the output under an error field if "Continue On Fail" is enabled. Otherwise, they will stop execution. Check API credentials and request body correctness.

Links and References

Discussion