Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

NH Server Config → Get One NH Server Config

AI-generated

Overview

This node interacts with the Halo PSA API to retrieve configuration details of a specific NH Server Config by its identifier. It is designed to fetch detailed or summary information about one NH Server Config based on user input.

Common scenarios where this node is beneficial include:

  • Automating retrieval of server configuration details for monitoring or auditing.
  • Integrating server config data into workflows for reporting or alerting.
  • Fetching configuration info dynamically to drive conditional logic in automation.

For example, you might use this node to get the full details of a particular NH Server Config by specifying its ID and whether to include detailed information, then use that data downstream in your workflow.

Properties

Name Meaning
Id The unique numeric identifier of the NH Server Config to retrieve.
Includedetails Whether to include detailed information in the response. This is sent as a query parameter.

Output

The node outputs JSON data representing the NH Server Config retrieved from the Halo PSA API. The structure corresponds to the API's response for a single NH Server Config, including all requested fields and optionally detailed subfields if Includedetails is set.

If the API returns an error, the output JSON will contain an error field with the error message.

No binary data output is produced by this operation.

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 API requests via HTTP headers.
  • No additional external dependencies are required beyond the configured API credentials.

Troubleshooting

  • Missing Credentials: If no credentials are provided or they are invalid, the node will throw an error "No credentials returned!" Ensure the API key credential is properly configured.
  • Resource or Operation Not Found: Errors like "Resource NH Server Config not found" or "Operation Get One NH Server Config not found for resource NH Server Config" indicate misconfiguration of resource or operation names.
  • Invalid Id Parameter: Providing an invalid or missing Id will cause the API request to fail. Make sure to supply a valid numeric ID.
  • API Request Failures: Network issues, incorrect credentials, or API downtime can cause request errors. The node will return the error message in the output JSON if "Continue On Fail" is enabled; otherwise, it will stop execution.
  • JSON Parsing Errors: If additional parameters are supplied as JSON strings, ensure they are correctly formatted to avoid parsing exceptions.

Links and References

Discussion