Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

MYOB Details → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API, allowing users to perform various operations on different resources within the Halo PSA system. Specifically, for the resource MYOB Details and operation Post Undefined, it sends a POST request with a JSON body to the corresponding API endpoint.

Typical use cases include synchronizing entity data such as clients, suppliers, or other mappings between n8n workflows and the Halo PSA platform. For example, you might use this node to update MYOB-related details by posting structured JSON data representing entities and their mappings.

Properties

Name Meaning
Body A JSON object containing the data to post. It includes arrays for sync_entities_list, client_mappings, and supplier_mappings. Each array holds objects representing the respective entities or mappings to be synchronized or updated in the Halo PSA system.

The property expects a JSON string that will be parsed and sent as the request body.

Example structure of the Body property:

{
  "sync_entities_list": [
    {}
  ],
  "client_mappings": [
    {}
  ],
  "supplier_mappings": [
    {}
  ]
}

Output

The node outputs an array of items where each item contains a json field holding the response from the Halo PSA API for the POST request made. The structure of the response depends on the API but generally reflects the result of the synchronization or update operation performed.

If an error occurs during the request, the output JSON will contain an error field with the error message, provided the node is configured to continue on failure.

No binary data output is produced by this node.

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 custom headers.
  • No additional external dependencies beyond the Halo PSA API and its authentication are required.

Troubleshooting

  • No credentials returned!
    This error indicates missing or invalid 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 the resource name is exactly "MYOB Details" and the operation is "Post Undefined". Typos or unsupported combinations will cause errors.

  • JSON parsing errors
    Since the Body property expects a JSON string, malformed JSON will cause parsing failures. Validate the JSON format before running the node.

  • API request failures
    Network issues, incorrect credentials, or invalid request bodies can cause the API to reject the request. Check the error messages returned in the output JSON for clues.

  • Continue on Fail
    If enabled, the node will output error messages instead of stopping execution, which helps in debugging batch operations.

Links and References

Discussion