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
This node integrates with the Druva MSP API to perform various operations on different resources, including Customers. Specifically, for the Customer - Get operation, it retrieves detailed information about a single customer identified by their unique Customer ID. This is useful in scenarios where you need to fetch customer details for reporting, auditing, or further processing within an automation workflow.
Practical examples include:
- Fetching customer profile data before creating related records.
- Validating customer existence and details during onboarding processes.
- Integrating customer data into dashboards or notifications.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer to retrieve. Options are dynamically loaded from the list of available customers. |
Output
The node outputs JSON data representing the customer details retrieved from the Druva MSP API. The structure typically includes all relevant fields describing the customer, such as their ID, account name, customer name, and other metadata provided by the API.
If the node supports binary data output (not indicated here), it would represent associated files or attachments related to the customer, 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 node uses the base URL
https://apis.druva.comfor API requests. - The "Customer ID" property options are dynamically loaded by querying the
/msp/v2/customersendpoint, requiring network access and valid credentials.
Troubleshooting
- Error fetching customers: If the dropdown for Customer ID fails to load, check API credentials and network connectivity.
- Resource not implemented error: Occurs if an unsupported resource is selected; ensure "Customer" is chosen for this operation.
- API request failures: May result from invalid Customer IDs or expired credentials. Verify the Customer ID exists and refresh API credentials if needed.
- Continue on Fail: If enabled, errors for individual items will be returned as JSON objects with an
errorfield instead of stopping execution.
Links and References
- Druva MSP API Documentation (general reference for API endpoints)
- n8n documentation on Creating Custom Nodes