Druva MSP icon

Druva MSP

Interact with the Druva MSP API
Join our community

Actions39

Overview

The node provides integration with the Druva MSP API, allowing users to manage various resources such as customers, tenants, service plans, tasks, events, admins, and reports. Specifically, for the Customer - Update operation, it enables updating details of an existing customer in the Druva MSP system. This includes modifying the customer's name, contact phone number, physical address, tenant administrators, and optionally enabling specific features like Security Posture and Observability.

This node is beneficial in scenarios where organizations need to automate the management of their customer data within Druva MSP, such as synchronizing customer information from other systems, bulk updating customer details, or programmatically managing tenant administrators associated with a customer.

Practical example:
An IT service provider wants to update the contact information and assigned tenant administrators for a customer after a recent organizational change. Using this node, they can automate the update process by providing the new details and selected tenant admins, ensuring the Druva MSP system reflects the latest customer configuration without manual intervention.

Properties

Name Meaning
Customer ID The unique identifier of the customer to update. This is required to specify which customer record will be modified.
Customer Name The updated name of the customer organization.
Phone Number The updated contact phone number for the customer, formatted as a string (e.g., +1-XXX-XXX-XXXX).
Address The updated physical address of the customer as a single string, including street, city, state, country, and postal code (e.g., "123 Main St, San Francisco, CA, USA 94105").
Tenant Admins A multi-select list of unique IDs representing tenant administrators who should manage the tenant for this customer. Selecting no admins removes all tenant admins from the customer. The list is dynamically loaded via API.
Update Features Boolean flag indicating whether to update the customer's feature settings.
Security Posture and Observability Boolean flag (shown only if "Update Features" is true) to enable or disable the Security Posture and Observability feature for the customer.

Output

The node outputs JSON data representing the result of the update operation on the customer resource. This typically includes confirmation of the updated customer details or any relevant response data returned by the Druva MSP API.

If the operation encounters errors, the output JSON will contain error messages describing the issue.

The node does not output binary data.

Dependencies

  • Requires an active connection to the Druva MSP API.
  • Requires an API authentication token or API key credential configured in n8n to authorize requests.
  • The node depends on the Druva MSP API endpoints for customers, tenant administrators, and feature toggles.
  • Network connectivity to https://apis.druva.com must be available.

Troubleshooting

  • Common issues:

    • Invalid or missing Customer ID: The update will fail if the specified customer ID does not exist or is incorrect.
    • Insufficient permissions: The API credentials used must have rights to update customer information.
    • Incorrect format for phone number or address may cause validation errors.
    • Selecting tenant admins that do not exist or are invalid IDs may cause errors.
    • If "Update Features" is enabled but no valid feature flags are set, the update might not apply as expected.

  • Error messages:

    • "The resource 'customer' is not implemented!": Indicates the node was called with an unsupported resource; ensure the resource parameter is correctly set to "customer".
    • API errors returned from Druva MSP will be passed through; check the message for details such as "Customer not found", "Unauthorized", or "Validation failed".

  • Resolution tips:

    • Verify the Customer ID exists in Druva MSP before attempting update.
    • Ensure API credentials have sufficient privileges.
    • Validate input formats for phone number and address.
    • Use the "List all administrators" API to get valid tenant admin IDs before selecting them.
    • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

  • Druva MSP API Documentation (general reference for API endpoints and data models)
  • n8n Documentation (for configuring credentials and using nodes)
  • Druva MSP support or developer portal for detailed API usage and troubleshooting guides

Discussion