Actions38
- Order Actions
- Product Actions
- Customer Actions
- Address Actions
- Special Offer Actions
- Coupon Actions
- Shipment Actions
- Digital Product Actions
Overview
This node integrates with the Salla.sa e-commerce platform API, allowing users to perform various operations on different resources such as orders, products, customers, addresses, special offers, coupons, shipments, and digital products. Specifically for the Customer - Get operation, the node retrieves detailed information about a single customer by their unique ID.
Common scenarios where this node is beneficial include:
- Fetching customer details to display or process in workflows.
- Integrating customer data retrieval into automated order processing or CRM systems.
- Using customer information to personalize marketing or support actions.
For example, you can use this node to get a customer's profile data by providing their ID, then use that data downstream in your workflow to send personalized emails or update records in another system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the customer to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the customer object retrieved from the Salla API. The structure typically includes all available customer details such as name, contact information, status, and other metadata as provided by the Salla platform.
If multiple items were returned (not applicable for the "Get" operation but relevant for "Get All"), the output would be an array of customer objects.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Salla.sa API using OAuth2 authentication credentials configured in n8n.
- The node depends on internal helper functions to make authenticated HTTP requests to the Salla API endpoints.
- Proper API permissions are needed to access customer data.
Troubleshooting
- Missing or invalid ID: If the "ID" property is empty or incorrect, the API will likely return an error indicating the resource was not found. Ensure the correct customer ID is provided.
- Authentication errors: If the OAuth2 credentials are missing, expired, or invalid, the node will fail to authenticate. Reconfigure or refresh the API credentials.
- API rate limits or downtime: Temporary failures may occur if the Salla API enforces rate limits or experiences outages. Retry after some time or check API status.
- Unsupported operation error: If the operation parameter is set incorrectly, the node throws an error stating the operation is not supported for customers. Make sure to select "Get" when intending to retrieve a single customer.
Links and References
- Salla API Documentation (official API docs for reference on customer endpoints)
- n8n OAuth2 Credential Setup (guide on configuring OAuth2 credentials in n8n)