Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Incoming Event → Delete Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Incoming Event resource and the Delete Undefined operation, it deletes an incoming event identified by its ID.

Common scenarios where this node is useful include automating the cleanup or removal of obsolete or incorrect incoming events in a PSA (Professional Services Automation) system. For example, if an incoming event was created by mistake or is no longer relevant, this node can programmatically delete it based on its unique identifier.

Practical example: Automatically deleting incoming events that meet certain criteria (e.g., older than a specific date or flagged as invalid) as part of a workflow to maintain data hygiene.

Properties

Name Meaning
Id The numeric identifier of the Incoming Event 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 incoming event. The output JSON typically contains confirmation of deletion or error details if the operation 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 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 authenticated HTTP requests to the Halo PSA REST API endpoints.

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 Incoming Event ID may result in an API error response.
    • Network connectivity issues or incorrect base URL configuration can cause request failures.

  • Error messages:

    • "No credentials returned!": Ensure that the API credentials are properly set up in n8n.
    • "Resource Incoming Event not found" or "Operation Delete Undefined not found for resource Incoming Event": Indicates a misconfiguration or unsupported operation/resource combination.
    • API errors returned from Halo PSA will appear in the output JSON under the error key if "Continue On Fail" is enabled; otherwise, they will cause the node to fail execution.

  • Resolution tips:

    • Verify all credential fields are correctly filled.
    • Confirm the Incoming Event ID exists in the Halo PSA system.
    • Check network access and API endpoint correctness.

Links and References

Discussion