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 "Tenant - Get" operation in this node allows users to retrieve detailed information about a specific tenant within the Druva MSP platform by providing the unique Tenant ID. This is useful for scenarios where you need to fetch tenant-specific data such as configuration, status, or metadata for further processing or reporting.
Practical examples include:
- Automating tenant audits by fetching tenant details regularly.
- Integrating tenant information into dashboards or other systems.
- Validating tenant existence or status before performing other operations.
Properties
| Name | Meaning |
|---|---|
| Tenant ID | Unique identifier of the tenant to fetch |
Output
The output JSON contains the detailed information of the requested tenant. The structure typically includes fields representing tenant attributes such as tenant name, tenant ID, status, type, and other metadata provided by the Druva MSP API.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the tenant, but this operation primarily returns JSON data.
Dependencies
- Requires an active connection to the Druva MSP API via an API key credential configured in n8n.
- The base URL for API requests is
https://apis.druva.com. - Proper permissions on the API key to access tenant information are necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Tenant ID will likely result in an error or empty response.
- Network connectivity problems or incorrect API credentials can cause authentication failures.
- Insufficient permissions on the API key may lead to authorization errors.
Error messages:
- Errors returned from the API will be surfaced with their message in the node's output.
- If the node throws an error like "The resource 'tenant' is not implemented!", it indicates a misconfiguration or unsupported resource selection.
Resolutions:
- Verify the Tenant ID is correct and exists in the Druva MSP environment.
- Check that the API key credential is valid and has required scopes.
- Ensure network connectivity to the Druva MSP API endpoint.
- Enable "Continue On Fail" in the node settings to handle errors gracefully during batch executions.
Links and References
- Druva MSP API Documentation (general reference): https://docs.druva.com/
- n8n Documentation on Credentials and API integrations: https://docs.n8n.io/credentials/