Druva MSP icon

Druva MSP

Interact with the Druva MSP API
Join our community

Actions39

Overview

The node enables interaction with the Druva MSP API, specifically allowing users to create a new customer record within the Druva MSP system. This operation is useful for organizations managing multiple customers or tenants through Druva's platform, automating the onboarding process by programmatically adding customer details.

Typical use cases include:

  • Automating customer creation during sales or onboarding workflows.
  • Integrating Druva MSP customer management into broader IT service management or CRM systems.
  • Ensuring consistent and accurate customer data entry without manual intervention.

For example, when a new client signs up, this node can be used to create their customer profile in Druva MSP, including contact information and administrative assignments.

Properties

Name Meaning
Customer Name The official name of the customer organization. This is required unless the "Hide Customer Name from Druva" option is enabled.
Hide Customer Name from Druva A boolean flag indicating whether to keep the real customer name private from Druva's internal systems. If true, the real customer name is hidden and an alternative name must be provided.
Alternative Name for Druva Systems The alternative name shown in Druva's internal systems instead of the real customer name. Required if hiding the real name. Note that this name cannot be changed after creation.
Phone Number Contact phone number for the customer, formatted as a string (e.g., +1-XXX-XXX-XXXX). Required.
Address The customer's physical address as a single string, including street, city, state, country, and postal code (e.g., "123 Main St, San Francisco, CA, USA 94105"). Required.
Tenant Admins A list of IDs representing tenant administrators who will manage the tenant for the customer. These are selected from available admins loaded dynamically. Optional but recommended for proper tenant management.

Output

The node outputs JSON data representing the newly created customer object as returned by the Druva MSP API. This typically includes fields such as the customer ID, names (real and/or alternative), contact details, address, and assigned tenant administrators.

If the node supports binary data output (not indicated here), it would represent associated files or attachments related to the customer, but this operation focuses on JSON metadata only.

Dependencies

  • Requires an active connection to the Druva MSP API via an API key credential configured in n8n.
  • The node depends on the Druva MSP API endpoints for customer creation and admin retrieval.
  • Network access to https://apis.druva.com must be available.
  • Proper permissions on the API key to create customers and assign tenant admins.

Troubleshooting

  • Missing Required Fields: Errors may occur if mandatory properties like Customer Name, Phone Number, or Address are missing. Ensure all required fields are filled.
  • Alternative Name Requirement: If "Hide Customer Name from Druva" is enabled, the alternative name must be provided; otherwise, the API will reject the request.
  • API Authentication Errors: Invalid or expired API credentials will cause authentication failures. Verify the API key and its permissions.
  • Network Issues: Connectivity problems to the Druva API endpoint will result in timeouts or unreachable errors.
  • Duplicate Customers: Attempting to create a customer with a name or alternative name that already exists might cause conflicts depending on API rules.
  • Immutable Alternative Name: Once set, the alternative name cannot be changed. Plan accordingly before creating the customer.

Links and References

Discussion