Salla icon

Salla

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

Actions38

Overview

This node interacts with the Salla.sa e-commerce platform API to retrieve address data. Specifically, the "Get All" operation for the "Address" resource fetches multiple addresses from the platform. It supports filtering by status, date range, and search terms, and allows users to either return all matching results or limit the number of returned addresses.

Common scenarios where this node is beneficial include:

  • Synchronizing address data from Salla into other systems.
  • Generating reports or analytics based on customer addresses.
  • Filtering addresses by status or date to target specific subsets.

For example, a user might want to retrieve all active addresses created after a certain date or search for addresses containing a particular keyword.

Properties

Name Meaning
Return All Whether to return all matching addresses or only up to a specified limit.
Limit Maximum number of addresses to return (applicable only if "Return All" is false). Range: 1-100.
Filters Collection of filters to narrow down results:
- Status: Filter by one or more statuses (Active, Inactive, Draft, Pending, Completed, Cancelled)
- Date From: Filter addresses created from this date/time onwards.
- Date To: Filter addresses created up to this date/time.
- Search: Text search term to filter addresses.

Output

The output is a JSON array where each item represents an address object retrieved from the Salla API. Each address object contains fields as defined by the Salla platform's address schema (not detailed in the source code).

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication credential configured in n8n to access the Salla API.
  • Uses internal helper functions to make authenticated HTTP requests to Salla endpoints.
  • The node depends on the sallaOAuth2Api credential (an OAuth2 API key credential) to authenticate requests.

Troubleshooting

  • Common issues:

    • Authentication errors if the API credential is missing or invalid.
    • Request limits exceeded if too many items are requested without proper pagination.
    • Invalid filter values may cause the API to reject the request.

  • Error messages:

    • Errors thrown by the node will typically indicate unsupported operations if the wrong operation is selected.
    • Network or API errors will be surfaced with their message; ensure network connectivity and valid credentials.

  • Resolutions:

    • Verify that the API credential is correctly set up and has necessary permissions.
    • Use the "Limit" property to restrict the number of results if not returning all.
    • Double-check filter values for correctness and supported options.

Links and References

Discussion