Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

PRTG Details → Delete Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the PRTG Details resource and the Delete Undefined operation, it deletes a PRTG detail entry identified by its unique ID.

Typical use cases include automating the cleanup or removal of obsolete or incorrect PRTG details from your system. For example, if you have monitoring data entries that are no longer valid or needed, this node can programmatically delete them based on their ID, helping maintain accurate and up-to-date monitoring configurations.

Properties

Name Meaning
Id The unique numeric identifier of the PRTG detail entry to delete. This is a required field.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output JSON contains the response from the Halo PSA API after attempting to delete the specified PRTG detail. If the deletion is successful, the response typically confirms the deletion; if there is an error, the JSON will contain an error field with the error message.

No binary data output is produced by this operation.

Dependencies

  • Requires credentials for authenticating with the Halo PSA API, including:

    • Base URL of the Halo PSA instance.
    • Tenant identifier.
    • Client ID.
    • Client Secret.

  • These credentials must be configured in n8n prior to using the node.

  • The node makes HTTP requests to the Halo PSA API endpoints using these credentials.

Troubleshooting

  • Common Issues:

    • Missing or invalid credentials will cause authentication failures.
    • Providing an invalid or non-existent Id may result in an error from the API indicating the resource was not found.
    • Network connectivity issues can prevent the node from reaching the Halo PSA API.

  • Error Messages:

    • "No credentials returned!": Indicates that the node could not retrieve the necessary API credentials. Ensure credentials are properly set up in n8n.
    • API errors returned in the JSON output under the error key provide details about what went wrong (e.g., invalid ID, permission denied).

  • Resolution Tips:

    • Verify that the API credentials are correct and have sufficient permissions.
    • Confirm that the Id corresponds to an existing PRTG detail entry.
    • Check network connectivity and firewall settings to allow outbound requests to the Halo PSA API.

Links and References

Discussion