Actions79
- Admin Actions
- Alert Summary Actions
- Backup Health Summary Actions
- Consumption Billing Analyzer Actions
- Customer Actions
- Event Actions
- Report - Cyber Resilience Actions
- Report - Endpoint Actions
- Report - Enterprise Workloads Actions
- Get Alert History Report
- Get Backup Activity Report
- Get DR Failback Activity Report
- Get DR Failover Activity Report
- Get DR Replication Activity Report
- Get Resource Status Report
- Get Storage Consumption by BackupSets Report
- Get Google Alerts Report
- Get Google License Usage Report
- Get Google Preserved Users Datasources Report
- Get Google Shared Drive Backup Activity Report
- Get Google Shared Drive Restore Activity Report
- Get Google Storage Consumption Report
- Get Google User Count and Status Report
- Get Google User Last Backup Status Report
- Get Google User Provisioning Report
- Get Google User Restore Activity Report
- Get Google User Workload Report
- Get M365 Alerts Report
- Get M365 Groups Backup Activity Report
- Get M365 Groups Discovery Report
- Get M365 License Usage Report
- Get M365 Preserved Users Datasources Report
- Get M365 Public Folder Backup Activity Report
- Get M365 SharePoint Backup Activity Report
- Get M365 SharePoint Site Discovery Report
- Get M365 Storage Consumption Report
- Get M365 Teams Backup Activity Report
- Get M365 Teams Discovery Report
- Get M365 User Count and Status Report
- Get M365 User Last Backup Status Report
- Get M365 User Provisioning Report
- Get M365 User Restore Activity Report
- Get M365 User Workload Report
- Report - Usage Actions
- Service Plan Actions
- Storage Region Actions
- Task Actions
- Tenant Actions
- Tenant Config - Enterprise Workloads Actions
- Tenant Config - inSync Actions
Customer → Create
AI-generatedOverview
This node operation creates a new customer in the Druva MSP system. It is useful for MSP administrators or automation workflows that need to programmatically add customer organizations to Druva's platform. For example, when onboarding a new client, this node can be used to set up the customer's profile, contact details, tenant admins, and optionally configure features and attributes during creation.
Use Case Examples
- Creating a new customer with a specified name, phone number, and address.
- Creating a customer while hiding the real customer name from Druva's internal systems by providing an alternative internal name.
- Assigning tenant administrators to manage the customer tenant during creation.
- Enabling specific features like Security Posture and Observability for the customer at creation time.
Properties
| Name | Meaning |
|---|---|
| Customer Name | Name of the customer organisation, required for creation. |
| Hide Customer Name from Druva | Boolean flag to keep the real customer name private from Druva's internal systems by using a different internal name. |
| 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. |
| Phone Number | Contact phone number for the customer, required for creation. |
| Address | Customer's physical address as a single string, required for creation. |
| Tenant Admins | IDs of tenant administrators who should manage the tenant for the customer. |
| Update Features | Boolean flag indicating whether to set customer features during creation. |
| Security Posture and Observability | Boolean flag to enable the Security Posture and Observability feature for this customer. Only applicable if Update Features is true. |
| Set Attributes | Boolean flag indicating whether to set customer-level attributes during creation. |
| Attributes | Customer-level attributes such as licenseManagementAllowed or dataAccessAllowed, with name and value pairs. Only applicable if Set Attributes is true. |
| Wrap Output Items | When enabled, wraps all output items into a single item containing an array to prevent the next node from executing multiple times. |
| Wrapper Property Name | The property name to use for the wrapped array of items in the output. Default is 'items'. |
Output
JSON
id- Unique identifier of the created customer.customerName- Name of the created customer organization.accountName- Alternative internal name used in Druva systems if the real name is hidden.phoneNumber- Contact phone number of the customer.address- Physical address of the customer.tenantAdmins- List of tenant administrator IDs assigned to the customer.features- Features enabled for the customer, such as Security Posture and Observability.attributes- Customer-level attributes set during creation.
Dependencies
- Druva MSP API with appropriate API key credentials
Troubleshooting
- Ensure all required fields (Customer Name, Phone Number, Address) are provided; missing required fields will cause errors.
- If 'Hide Customer Name from Druva' is enabled, the 'Alternative Name for Druva Systems' must be provided and cannot be changed after creation.
- API authentication errors may occur if the Druva MSP API credentials are invalid or expired; verify credentials.
- Network or API endpoint issues can cause request failures; check connectivity and API base URL.
- If 'Update Features' or 'Set Attributes' are enabled, ensure the feature flags and attribute names/values are valid according to Druva's documentation.
Links
- Druva MSP Customer Attributes Documentation - Reference for valid customer-level attribute names and values.