Salla icon

Salla

Interact with Salla.sa e-commerce platform API
Join our community

Actions38

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 resource with the 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 personalize marketing or support workflows.
  • Integrating customer data into CRM systems or other business tools.
  • Automating customer data retrieval for order processing or analytics.

Practical example:

  • You want to retrieve a customer's profile information based on their ID to update your internal database or trigger follow-up actions in your workflow.

Properties

Name Meaning
ID The unique identifier of the customer to retrieve. This is a required string input.

Output

The node outputs a JSON object representing the customer data retrieved from the Salla API. The structure corresponds directly to the customer resource schema defined by Salla, typically including fields such as customer name, email, contact details, status, and other relevant attributes.

If multiple items were returned (not applicable for the "Get" operation), they would be output as an array of JSON 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 the sallaApiRequest helper function to make authenticated HTTP requests to the Salla API endpoints.
  • Proper API permissions are needed to access customer data.

Troubleshooting

  • Error: "The operation 'get' is not supported for customers!"
    This error indicates an unsupported operation was requested. Ensure the operation parameter is set correctly to "get" for the Customer resource.

  • API Authentication Errors
    If the node fails due to authentication issues, verify that the OAuth2 credentials are valid and have not expired.

  • Invalid or Missing ID
    Providing an empty or incorrect customer ID will result in API errors. Make sure the ID property is correctly set and corresponds to an existing customer.

  • Network or API Availability Issues
    Temporary network failures or API downtime can cause request failures. Retry after some time or check the API status.

Links and References

Discussion