Actions39
- Admin Actions
- Consumption Billing Analyzer Actions
- Customer Actions
- Event Actions
- Report - Cyber Resilience Actions
- Report - Endpoint Actions
- Report - Hybrid Workloads Actions
- Report - Usage Actions
- Service Plan Actions
- Task Actions
- Tenant Actions
Overview
The node interacts with the Druva MSP API to manage various resources, including tenants. Specifically, for the Tenant resource, it supports operations such as suspending a tenant. The Suspend operation allows users to temporarily disable or pause a tenant's services within the Druva MSP platform.
This node is beneficial in scenarios where administrators need to control tenant access or service availability programmatically, such as during maintenance windows, compliance checks, or billing adjustments.
Example use case:
An IT administrator wants to suspend a tenant's account automatically when certain conditions are met (e.g., non-payment or security concerns). Using this node, they can trigger the suspend operation and optionally wait for its completion before proceeding with further workflow steps.
Properties
| Name | Meaning |
|---|---|
| Tenant ID | Unique identifier of the tenant to be suspended. |
| Wait for Completion | Whether to wait for the suspend operation to complete before returning the result. (true/false) |
Output
The node outputs JSON data representing the result of the suspend operation on the specified tenant. This typically includes details about the tenant's updated status or confirmation that the suspension was successful.
If the "Wait for Completion" property is set to true, the output will reflect the final state after the suspend operation completes. Otherwise, it may return an immediate acknowledgment that the suspend request was accepted.
The node does not output binary data.
Dependencies
- Requires an active connection to the Druva MSP API.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- The base URL for API requests is
https://apis.druva.com.
Troubleshooting
Common issues:
- Invalid or missing Tenant ID: Ensure the Tenant ID provided exists and is correctly formatted.
- Authentication errors: Verify that the API credentials are valid and have sufficient permissions.
- Network or API downtime: Check connectivity and Druva MSP service status.
Error messages:
"The resource 'tenant' is not implemented!"— This indicates an internal error if the resource parameter is incorrect; ensure the resource is set to "tenant".- API errors returned from Druva MSP (e.g., 4xx or 5xx HTTP responses) will be surfaced as node errors. Review the error message for details and verify API usage limits or permissions.
Links and References
- Druva MSP API Documentation (general reference for API endpoints and operations)
- n8n documentation on creating custom nodes