Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

SQL Import → 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 SQL Import resource and the Post Undefined operation, it enables sending a JSON body payload to the API endpoint associated with SQL import functionality.

Typical use cases include automating data imports into Halo PSA via SQL commands or structured JSON data, which can be useful for synchronizing external databases, bulk updating records, or integrating third-party systems that export data in SQL-compatible formats.

For example, a user might configure this node to post a JSON object containing fields and client ID lists to import or update data in Halo PSA without manual intervention.

Properties

Name Meaning
Body A JSON object representing the request payload to send to the SQL Import endpoint. It typically includes arrays such as fields (defining the data fields) and halointegrator_allowed_clientids_list (specifying allowed client IDs). The property expects valid JSON input.

Output

  • The node outputs an array of JSON objects corresponding to each input item processed.
  • Each output item contains a json field holding the response from the Halo PSA API for the SQL Import POST request.
  • If the request fails and "Continue On Fail" is enabled, the output will contain an error message inside the json.error field.
  • No binary data output is produced by this node.

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.
  • Network access to the Halo PSA API endpoint is necessary.
  • No additional external dependencies beyond the n8n environment and the provided credentials.

Troubleshooting

  • No credentials returned!: This error occurs if the node cannot retrieve the required API authentication details. Ensure that the API key credential is properly configured and connected.
  • Resource or Operation not found: Indicates misconfiguration of the resource or operation parameters. Verify that "SQL Import" is selected as the resource and "Post Undefined" as the operation.
  • Invalid JSON in Body: Since the Body property expects JSON, malformed JSON will cause parsing errors. Validate the JSON syntax before running the node.
  • API Request Failures: Network issues, incorrect credentials, or invalid request payloads may cause the API call to fail. Check the error messages returned in the output and verify connectivity and payload correctness.
  • Enabling "Continue On Fail" allows the workflow to proceed even if some requests fail, capturing error details in the output.

Links and References

Discussion