Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

N Central Details → Delete Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the N Central Details resource with the Delete Undefined operation, it deletes an entity identified by a numeric ID. This is useful in scenarios where you need to programmatically remove specific N Central detail records from your Halo PSA system.

Practical examples include:

  • Automating cleanup of obsolete or incorrect N Central details.
  • Integrating with other workflows that require deletion of N Central details based on external triggers or conditions.

Properties

Name Meaning
Id The numeric identifier of the N Central detail record to delete.

Output

The node outputs JSON data representing the response from the Halo PSA API after attempting the deletion. Typically, this will confirm success or provide error details if the deletion failed.

If the operation fails 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, tenant identifier, client ID, and client secret.
  • The node makes authenticated HTTP requests to the Halo PSA API endpoints.
  • Proper configuration of these credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Missing or invalid credentials will cause the node to throw an error indicating no credentials were returned.
    • Providing an invalid or non-existent ID may result in an API error response.
    • Network connectivity problems can cause request failures.
  • Error messages:

    • "No credentials returned!": Ensure that the Halo PSA API credentials are correctly configured and accessible.
    • Errors returned from the API (e.g., "Resource not found", "Unauthorized") will be included in the output JSON if "Continue On Fail" is enabled; otherwise, they will cause the node to fail.
  • Resolution tips:

    • Verify the correctness of the provided ID.
    • Check API credentials and permissions.
    • Enable "Continue On Fail" during testing to capture error details without stopping the workflow.

Links and References

Discussion