Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Azure AD Connection → Delete Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Azure AD Connection resource and the Delete Undefined operation, it deletes an Azure Active Directory connection identified by a numeric ID.

Common scenarios where this node is useful include automating management of Azure AD connections within Halo PSA, such as cleaning up obsolete or invalid connections programmatically. For example, you might use this node in a workflow that periodically removes unused Azure AD connections based on certain criteria.

Properties

Name Meaning
Id The numeric identifier of the Azure AD Connection 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 Azure AD Connection. The output structure typically contains confirmation of deletion or error details if the operation failed.

If the operation encounters an error 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 HTTP requests to the Halo PSA API endpoints, so network access to the API server is necessary.

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 Azure AD Connection ID will likely result in an API error.
    • Network connectivity issues can cause request failures.

  • Error Messages:

    • "No credentials returned!": Ensure that the API credentials are properly set up in n8n.
    • 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 execution.

  • Resolution Tips:

    • Verify that the Azure AD Connection ID exists before attempting deletion.
    • Confirm that the API credentials have sufficient permissions to delete Azure AD Connections.
    • Check network connectivity and firewall settings to allow outbound requests to the Halo PSA API.

Links and References

Note: The above summary is based solely on static analysis of the provided source code and input properties. Runtime behavior may depend on actual API responses and environment configuration.

Discussion