Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Tax Rule → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Tax Rule resource and the Post Undefined operation, it sends a POST request with a JSON body to create or update tax rules based on provided conditions.

Typical use cases include automating tax rule management within an IT service management or professional services automation workflow. For example, you might define complex tax conditions programmatically and push them to Halo PSA without manual entry, enabling dynamic tax calculations or compliance updates.

Properties

Name Meaning
Body A JSON object representing the tax rule details to be sent in the request body. It supports defining tax_conditions with nested value_lookup arrays. The property expects valid JSON input describing the tax rule structure.

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 creating or updating the tax rule.
  • If an error occurs and "Continue On Fail" is enabled, the output will contain an error field with the error message instead.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Halo PSA API.
  • Needs configuration of base URL, tenant identifier, client ID, and client secret as part of the credentials.
  • Uses HTTP requests with appropriate headers (X-Tenant, X-HaloPSA-ClientId, X-HaloPSA-ClientSecret) to communicate with the Halo PSA backend.

Troubleshooting

  • No credentials returned!: This error indicates missing or misconfigured API authentication credentials. Ensure that the required API key and related parameters are correctly set up in n8n.
  • Resource or Operation not found: Occurs if the specified resource or operation does not exist in the node's configuration. Verify that "Tax Rule" and "Post Undefined" are correctly selected.
  • JSON parsing errors: Since the Body property expects JSON, invalid JSON syntax will cause failures. Validate JSON format before execution.
  • API request failures: Network issues, incorrect endpoint URLs, or authorization problems can cause request errors. Check connectivity and credential validity.
  • Enabling "Continue On Fail" allows the workflow to proceed despite individual item errors, returning error messages in the output for troubleshooting.

Links and References

Discussion