Distru icon

Distru

Interact with the Distru API

Overview

This node integrates with the Distru API to retrieve or manipulate various business-related data entities such as products, companies, orders, contacts, batches, and more. Specifically, the Get Product operation fetches product information from Distru, supporting filtering and pagination.

Typical use cases include:

  • Synchronizing product data from Distru into other systems.
  • Automating inventory or catalog updates by retrieving product details.
  • Building workflows that require up-to-date product information for reporting or processing.

For example, you might use this node to get a list of products updated after a certain date or to paginate through large product catalogs efficiently.

Properties

Name Meaning
Additional Fields Optional filters and pagination controls for the product query:
- Inserted Datetime: Filter products created after this datetime.
- Updated Datetime: Filter products updated after this datetime.
- Page Number: The page number of results to return (for pagination). Default is 1.
- Page Size: Number of results per page (for pagination). Default is 100.

Output

The output is an array of items where each item contains a json field holding product data retrieved from the Distru API.

  • If a specific product ID is provided, the output will contain one item with the detailed product JSON.
  • If no specific ID is given, the output will be a list of products matching the filter criteria, each as a separate item.
  • The structure of each product JSON corresponds directly to the Distru API's product object schema.
  • No binary data is returned by this operation.

Example output snippet (simplified):

[
  {
    "json": {
      "id": "00000000-0000-0000-0000-abcdef123456",
      "name": "Product Name",
      "sku": "SKU123",
      "description": "Product description",
      ...
    }
  },
  ...
]

Dependencies

  • Requires an API token credential for authenticating requests to the Distru API.
  • The node uses the Distru public API endpoint; optionally, it can target a staging environment if configured.
  • No additional external dependencies are required beyond the API token.

Troubleshooting

  • Missing API Token: The node will throw an error if the API token credential is not set. Ensure you have configured the API token in the node credentials.
  • Invalid Product ID Format: Product IDs are normalized to UUID format internally. Providing an invalid ID may result in no data returned or errors.
  • Pagination Issues: If you request a page number beyond available pages, the API may return empty results. Adjust page size and number accordingly.
  • API Errors: Network issues or invalid parameters may cause API request failures. Check the error message returned and verify your input parameters and network connectivity.
  • Continue on Fail: If enabled, the node will continue processing remaining items even if some fail, returning error messages in the output JSON.

Links and References

Discussion