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 to retrieve customer data. Specifically, the "Customer" resource with the "Get All" operation allows users to fetch multiple customer records from their Salla store.

Common scenarios for this node include:

  • Synchronizing customer lists from Salla into a CRM or marketing tool.
  • Generating reports or analytics based on customer data.
  • Filtering customers by status, date range, or search terms for targeted actions.

For example, a user might want to get all active customers who registered within a specific date range or search for customers matching a particular keyword.

Properties

Name Meaning
Return All Whether to return all customer results or limit the number of returned customers.
Limit Maximum number of customer records to return if not returning all (minimum 1, maximum 100).
Filters Collection of filters to narrow down the customer list:
- Status Filter customers by one or more statuses: Active, Inactive, Draft, Pending, Completed, Cancelled.
- Date From Filter customers created or updated from this date/time onward.
- Date To Filter customers created or updated up to this date/time.
- Search Search term to filter customers by matching text fields.

Output

The node outputs an array of JSON objects representing customer records retrieved from the Salla API. Each object contains detailed customer information as provided by the API, such as customer ID, name, email, status, creation date, and other relevant fields.

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication token configured in n8n credentials to access the Salla API.
  • Uses internal helper functions to make authenticated HTTP requests to the Salla API endpoints.
  • The node depends on the Salla API being available and responsive.

Troubleshooting

  • Common issues:

    • Authentication errors due to missing or invalid API credentials.
    • API rate limits or timeouts causing incomplete data retrieval.
    • Incorrect filter values leading to empty result sets.

  • Error messages:

    • Errors indicating unsupported operations will not occur here since "Get All" is supported.
    • Network or API errors will be surfaced with their message; ensure network connectivity and valid credentials.
    • If the node is set to not continue on failure, any error will stop execution; enabling "Continue On Fail" can help handle partial failures gracefully.

  • Resolutions:

    • Verify that the API key or OAuth2 token is correctly configured.
    • Check filter parameters for correctness and adjust limits if necessary.
    • Use the "Return All" option carefully to avoid large data loads that may cause timeouts.

Links and References

Discussion