Actions16
Overview
This node interacts with a cloud commerce platform to perform various operations on multiple resources such as customers, subscriptions, orders, and plans. Specifically, for the Customer - Get operation, it retrieves detailed information about a single customer by their unique Customer ID.
Common scenarios where this node is beneficial include:
- Fetching customer details to display or process in workflows.
- Integrating customer data retrieval into automated billing or support processes.
- Synchronizing customer information between systems.
For example, you might use this node to get a customer's profile before updating their subscription or generating an invoice.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer to retrieve. This is a required string input. |
Output
The output is a JSON object representing the retrieved customer data. The structure depends on the external API's response but typically includes fields such as customer name, contact details, status, and other relevant attributes.
If the node encounters an error during execution (e.g., invalid Customer ID), the output will contain an error field with a descriptive message.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token or key configured in n8n to access the cloud commerce platform.
- Depends on an initialized API service client that handles communication with the external platform.
- Uses a resource registry internally to manage available resources and their operations.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Customer ID will result in an error.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity problems can prevent successful API calls.
Error messages:
"Resource Customer not found or not yet migrated"indicates the node does not recognize the requested resource, possibly due to misconfiguration or version mismatch.- Errors containing
"Unknown error occurred"suggest unexpected failures; checking logs and API responses is recommended.
Resolutions:
- Verify the Customer ID is correct and exists in the system.
- Ensure API credentials are properly set up and have sufficient permissions.
- Check network connectivity and API endpoint availability.
- Enable "Continue On Fail" in the node settings to handle errors gracefully within workflows.
Links and References
- Refer to your cloud commerce platform’s official API documentation for detailed customer data schema and authentication setup.
- n8n documentation on creating custom nodes for further customization guidance.