Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Business Central 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 "Business Central Details" resource and the "Post Undefined" operation, it sends a POST request with a JSON body to the corresponding API endpoint.

Typical use cases include synchronizing or updating business central details such as environment settings, company information, client mappings, item group mappings, and synchronization entity lists in Halo PSA. This can be useful for automating data integration between Halo PSA and other systems, ensuring that business central configurations are kept up-to-date programmatically.

For example, a user might use this node to push updated client mappings or sync entity configurations from an external ERP system into Halo PSA automatically.

Properties

Name Meaning
Body A JSON object representing the payload sent in the POST request. It includes fields like environment, company, client_mappings, item_group_mappings, and sync_entities_list. The user provides this JSON structure, which is parsed and sent as the request body.

The property expects a JSON input structured similarly to:

{
  "environment": {},
  "company": {},
  "client_mappings": [{}],
  "item_group_mappings": [{}],
  "sync_entities_list": [{}]
}

Output

The node outputs an array of JSON objects, each corresponding to the response from the Halo PSA API for each input item processed. Each output item contains a json field holding the parsed JSON response from the API.

If the API call fails and the node is configured to continue on failure, the output will contain an error message inside the json.error field instead.

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 n8n's HTTP request capabilities.

Troubleshooting

  • Missing Credentials: If no credentials are provided or they are invalid, the node throws an error "No credentials returned!" Ensure that the API key credential is properly configured in n8n.
  • Resource or Operation Not Found: Errors like "Resource Business Central Details not found" or "Operation Post Undefined not found for resource Business Central Details" indicate misconfiguration of resource or operation names.
  • Invalid JSON in Body: Since the body is parsed from a JSON string, malformed JSON will cause parsing errors. Validate the JSON syntax before running the node.
  • API Request Failures: Network issues, incorrect authentication, or invalid request bodies may cause API errors. These errors are returned in the output under json.error if "Continue On Fail" is enabled; otherwise, the node execution stops with an error.
  • Path Parameter Replacement: The code supports dynamic replacement of path parameters in the endpoint URL. Missing required parameters will cause errors.

Links and References

Discussion