Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Std Request → 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 "Std Request" resource and the "Post Undefined" operation, it sends a POST request with a customizable JSON body to the Halo PSA API endpoint.

Typical use cases include automating the creation or updating of standard requests in Halo PSA by sending complex structured data such as creation rules, todo lists, custom fields, assets, users, budgets, services, milestones, and other related entities. This is useful for IT service management workflows, project tracking, or asset management where detailed request data needs to be programmatically submitted.

Example scenario: Automatically creating a new standard request with associated tasks, custom fields, and user attachments when triggered by an external event or another workflow step.

Properties

Name Meaning
Body A JSON object representing the full payload to send in the POST request. It can include nested arrays and objects such as creation rules, todo lists, custom fields, assets, users, budgets, services, access control, automation criteria, milestones, additional agents, audits, changes, date dependencies, optional custom fields, and optional assets. The structure must conform to the expected schema of the Halo PSA API for standard requests.

The property supports entering raw JSON, which will be parsed and sent as the request body.

Output

  • The node outputs the JSON response received from the Halo PSA API after making the POST request.
  • Each item in the output corresponds to one input item processed.
  • If the request involves binary data (not applicable here for this operation), it would handle that accordingly, but for this operation, only JSON responses are returned.
  • In case of errors, if "Continue On Fail" is enabled, the output will contain an error message in the JSON field for the respective item.

Dependencies

  • Requires an API key credential for authenticating with the Halo PSA API. This includes base URL, tenant identifier, client ID, and client secret.
  • The node uses HTTP requests with appropriate headers including authentication tokens.
  • No additional external libraries beyond those bundled with n8n and the included OpenAPI helper classes are required.

Troubleshooting

  • No credentials returned!: Ensure that the API key credential is properly configured and connected in n8n.
  • Resource or Operation not found: Verify that the selected resource and operation exist and are spelled correctly.
  • Invalid JSON in Body: The Body property expects valid JSON. Malformed JSON will cause parsing errors before the request is sent.
  • API request failures: Check network connectivity, API endpoint correctness, and that the provided credentials have sufficient permissions.
  • Error messages from API: These will be returned in the JSON output. Review the API documentation for specific error codes and meanings.
  • If "Continue On Fail" is disabled, any error will stop execution; enable it to handle errors gracefully per item.

Links and References

Discussion