Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Email Store → Delete Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Email Store resource and the Delete Undefined operation, it deletes an email store entry identified by a numeric ID.

Common scenarios where this node is beneficial include automating the management of email storage entries within Halo PSA, such as cleaning up obsolete or undefined email records programmatically.

Practical example: Automatically deleting an email store record by its ID when it is no longer needed or flagged as undefined in your system, helping maintain data hygiene without manual intervention.

Properties

Name Meaning
Id The numeric identifier of the email store entry to delete. This property is required.

Output

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

No binary data output is produced by this operation.

Example output JSON might look like:

{
  "success": true,
  "message": "Email store entry deleted successfully",
  "id": 123
}

or in case of failure:

{
  "error": "Entry not found"
}

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.
  • No additional external dependencies beyond the Halo PSA API are required.

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 error from the API stating that the entry was not found.
    • Network connectivity problems can cause request failures.

  • Error messages and resolutions:

    • "No credentials returned!": Ensure that the API authentication credentials are correctly configured in n8n.
    • "Resource Email Store not found" or "Operation Delete Undefined not found for resource Email Store": Verify that the resource and operation names are correct and supported.
    • API errors related to deletion (e.g., entry not found): Confirm that the provided ID exists and is correct.
    • If the node is set to continue on fail, errors will be included in the output JSON under an error key instead of stopping execution.

Links and References

Discussion