Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Journey → Delete Undefined

AI-generated

Overview

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

Common scenarios where this node is useful include automating the management of customer journeys or workflows within the Halo PSA system, such as cleaning up obsolete or test journeys by deleting them programmatically.

Practical example: Automatically delete a Journey by its ID when it is no longer needed, triggered as part of a workflow cleanup process.

Properties

Name Meaning
Id The numeric identifier of the Journey to delete. This property is required.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output JSON contains the response from the Halo PSA API after attempting to delete the specified Journey. If successful, the response typically confirms deletion; if an error occurs, the 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 and Client Secret for authentication

  • 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 helper.

Troubleshooting

  • Common issues:

    • Missing or invalid credentials will cause the node to throw an error "No credentials returned!".
    • Providing an invalid Journey ID (e.g., non-existent or unauthorized) may result in API errors.
    • Network connectivity problems can cause request failures.

  • Error messages:

    • "Resource Journey not found" or "Operation Delete Undefined not found for resource Journey" indicate misconfiguration of resource or operation parameters.
    • API error responses are passed through in the output JSON under an error key if "Continue On Fail" is enabled.

  • Resolutions:

    • Ensure that the API credentials are correctly configured and have sufficient permissions.
    • Verify that the Journey ID exists and is accessible.
    • Check network connectivity and API endpoint availability.
    • Use "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion