Druva MSP icon

Druva MSP

Interact with the Druva MSP API
Join our community

Actions39

Overview

The "Unsuspend Tenant" operation in this node interacts with the Druva MSP API to unsuspend a specified tenant. This is useful in scenarios where a tenant's services have been temporarily suspended (e.g., due to billing issues or administrative actions) and need to be reactivated to restore normal operations.

Practical examples include:

  • Automatically unsuspending tenants after payment confirmation.
  • Reactivating tenants following manual review or resolution of compliance issues.
  • Integrating tenant lifecycle management workflows that control suspension states.

Properties

Name Meaning
Tenant ID Unique identifier of the tenant to be unsuspended.
Wait for Completion Whether the node should wait until the unsuspend operation completes before returning.

Output

The node outputs JSON data representing the result of the unsuspend operation on the tenant. This typically includes details about the tenant's updated status or confirmation that the unsuspension was successful.

If the "Wait for Completion" property is set to true, the output will reflect the final state after the operation completes; otherwise, it may return immediately with an initiation acknowledgment.

No binary data output is indicated by the source code.

Dependencies

  • Requires an API key credential configured in n8n to authenticate with the Druva MSP API.
  • The node makes HTTP requests to the Druva MSP API endpoint at https://apis.druva.com.
  • Proper permissions are needed on the API key to perform tenant unsuspension operations.

Troubleshooting

  • Common Issues:

    • Invalid or missing Tenant ID: The operation requires a valid tenant identifier; ensure the correct ID is provided.
    • Insufficient API permissions: The API key must have rights to modify tenant states.
    • Network or API errors: Connectivity issues or API downtime can cause failures.

  • Error Messages:

    • Errors thrown during execution will include messages from the API or internal validation.
    • If "Continue On Fail" is enabled, errors for individual items will be returned as JSON objects with an error field describing the issue.

  • Resolution Tips:

    • Verify the tenant ID exists and is correctly formatted.
    • Check API credentials and their permissions.
    • Review network connectivity and API service status.
    • Enable detailed logging if available to capture request/response details.

Links and References

Discussion