Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Sla Head → Delete Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Sla Head resource and the Delete Undefined operation, it deletes an SLA Head entity identified by a numeric ID.

Common scenarios where this node is useful include automating the management of service level agreements (SLAs) within IT service management workflows. For example, you might use it to programmatically remove obsolete or undefined SLA entries from your system as part of cleanup or maintenance automation.

Properties

Name Meaning
Id The unique numeric identifier of the SLA Head record to delete. This property is required.

Output

The node outputs JSON data representing the response from the Halo PSA API after attempting to delete the specified SLA Head. The structure typically contains confirmation of deletion or error details if the operation failed.

If the operation encounters an error and "Continue On Fail" is enabled, 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 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 uses HTTP requests to communicate with the Halo PSA REST API endpoints.

Troubleshooting

  • Common issues:

    • Missing or invalid credentials will cause the node to throw an error stating "No credentials returned!".
    • Providing an invalid or non-existent SLA Head ID may result in an API error indicating the resource was not found.
    • Network connectivity problems can cause request failures.

  • Error messages:

    • "Resource Sla Head not found" or "Operation Delete Undefined not found for resource Sla Head" indicate misconfiguration of resource or operation parameters.
    • API errors returned from Halo PSA are passed through in the output JSON under an error field if "Continue On Fail" is enabled.

  • Resolution tips:

    • Verify that the SLA Head ID exists and is correct.
    • Ensure credentials are properly set up and have sufficient permissions.
    • Check network connectivity and API endpoint accessibility.
    • Enable "Continue On Fail" to handle errors gracefully during batch executions.

Links and References

Discussion