Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Std Request → Delete Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Std Request resource with the Delete Undefined operation, it sends a DELETE request to remove an entity identified by its ID. This is useful in scenarios where you need to programmatically delete standard requests or similar records from the Halo PSA system.

Practical examples include:

  • Automatically cleaning up obsolete or test requests.
  • Removing entries based on workflow conditions.
  • Integrating deletion steps into larger automation processes involving Halo PSA data.

Properties

Name Meaning
Id The numeric identifier of the standard request to be deleted. This is a required field.

Output

The node outputs JSON data representing the response from the Halo PSA API after attempting the deletion. Typically, this will contain confirmation of the deletion or details about the deleted entity. If the deletion fails, the output JSON will include an error message describing the failure.

No binary data output is produced by this operation.

Dependencies

  • Requires valid credentials to access the Halo PSA API, including base URL, tenant identifier, client ID, and client secret.
  • The node uses these credentials to authenticate API requests via HTTP headers.
  • No additional external dependencies beyond the Halo PSA API and n8n's HTTP request capabilities.

Troubleshooting

  • Common issues:

    • Missing or invalid credentials will cause authentication failures.
    • Providing an invalid or non-existent Id may result in errors from the API indicating the resource was not found.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • "No credentials returned!" — Ensure that the API credentials are properly configured in n8n.
    • Errors returned from the API (e.g., "Resource not found") indicate issues with the provided Id or permissions.
    • JSON parsing errors might occur if input parameters are malformed; ensure the Id is a valid number.

  • Resolution tips:

    • Double-check the API credentials and their permissions.
    • Verify the Id corresponds to an existing standard request.
    • Use the "Continue On Fail" option in n8n to handle errors gracefully within workflows.

Links and References

Discussion