Actions28
- Product Actions
- Product Stock Actions
Overview
This node integrates with the Tiny ERP API to manage product data. Specifically, the "Get Many" operation under the "Product" resource allows users to retrieve multiple products from their Tiny ERP system based on various search criteria and filters.
Typical use cases include:
- Fetching a list of active products for inventory or catalog synchronization.
- Searching products by partial name, code, or GTIN to display in an external application.
- Retrieving products created or modified within specific date ranges.
- Paginating through large product lists using limit and offset parameters.
For example, a user might want to get up to 100 active products whose names contain "coffee" and were modified after a certain date to update their online store's product listings.
Properties
| Name | Meaning |
|---|---|
| Code | Search products by their product code (exact match). |
| Creation Date | Filter products by their creation date. |
| GTIN | Search products by their GTIN barcode. |
| Limit | Maximum number of products to return (minimum 1). |
| Modification Date | Filter products by their last modification date. |
| Name | Search products by partial or complete product name. |
| Offset | Number of products to skip before starting to collect the result set (for pagination). |
| Status | Filter products by status: Active or Inactive. |
These properties are provided inside the "Additional Fields" collection when performing the "Get Many" operation on the "Product" resource.
Output
The output is an array of JSON objects representing the products retrieved from Tiny ERP. Each item corresponds to one product and contains all the fields returned by the Tiny ERP API for that product.
The structure of each product object depends on the API response but typically includes identifiers, names, codes, GTINs, status, creation/modification dates, and other product details.
No binary data is output by this operation.
Dependencies
- Requires an API authentication credential configured in n8n to connect to the Tiny ERP API.
- The node uses HTTP requests to communicate with Tiny ERP endpoints.
- No additional external dependencies beyond the configured API credentials.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Using invalid filter values (e.g., wrong date format) may result in API errors.
- Requesting too many records without proper pagination can lead to timeouts or rate limiting.
Error messages:
"The operation "getAll" is not supported!"— indicates a misconfiguration or unsupported operation; ensure the correct resource and operation are selected.- Network or authentication errors usually indicate problems with the API key or connectivity.
Resolutions:
- Verify API credentials and permissions.
- Use valid date formats (ISO 8601) for date filters.
- Use reasonable limits and offsets to paginate results.
Links and References
- Tiny ERP API Documentation (official API docs for reference)
- n8n Documentation (for general usage of nodes and credentials)