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 → Update
AI-generatedOverview
This node operation updates an existing customer in the Druva MSP system. It allows users to modify customer details such as the customer name, phone number, physical address, tenant administrators, and optionally update customer features and attributes. This operation is useful for managing customer information dynamically within an automation workflow, for example, updating contact details or changing administrative access for a customer organization.
Use Case Examples
- Updating the phone number and address of a customer after receiving new contact information.
- Changing the list of tenant administrators responsible for managing a customer's tenant.
- Enabling or disabling specific features like Security Posture and Observability for a customer.
- Modifying customer-level attributes such as license management or data access permissions.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique ID of the customer to update, used to identify which customer record to modify. |
| Customer Name | The name of the customer organization to update. |
| Phone Number | The contact phone number for the customer, formatted as a string (e.g., +1-XXX-XXX-XXXX). |
| Address | The customer's physical address as a single string, including street, city, state, country, and postal code. |
| Tenant Admins | A multi-select list of unique IDs of tenant administrators who should manage the tenant for the customer. Selecting none removes all tenant admins from the customer. |
| Update Features | Boolean flag indicating whether to update the customer's features. |
| Security Posture and Observability | Boolean flag to enable or disable the Security Posture and Observability feature for the customer. Only shown if 'Update Features' is true. |
| Update Attributes | Boolean flag indicating whether to update customer-level attributes such as license management or data access permissions. |
| Attributes | A collection of customer-level attributes to update, each with a name and value. Valid attribute names and values are documented externally. |
| 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'. Only shown if 'Wrap Output Items' is true. |
Output
JSON
jsoncustomerId- The unique identifier of the updated customer.customerName- The updated name of the customer organization.phoneNumber- The updated contact phone number for the customer.address- The updated physical address of the customer.tenantAdmins- The list of tenant administrator IDs managing the customer's tenant after update.features
*securityPostureAndObservability- Indicates if the Security Posture and Observability feature is enabled for the customer.attributes- The updated customer-level attributes with their names and values.
Dependencies
- An API key credential for Druva MSP API authentication is required.
Troubleshooting
- If the customer ID is invalid or not found, the node will throw an error indicating the customer could not be updated. Verify the customer ID is correct.
- If required fields like Customer Name, Phone Number, or Address are missing or incorrectly formatted, the API may reject the update request.
- When updating tenant administrators, ensure the selected admin IDs exist and are valid; otherwise, the update may fail or remove admins unintentionally.
- If the 'Update Features' or 'Update Attributes' flags are set incorrectly, the node may not update those sections as expected. Double-check these flags before running the node.
- API rate limits or network issues may cause request failures; enabling 'Continue On Fail' can help handle intermittent errors gracefully.
Links
- Druva MSP Customer Attributes Documentation - Documentation for valid customer-level attribute names and values used in the update operation.