Actions14
Overview
This node interacts with the Tiny ERP API to retrieve multiple product records based on various filtering criteria. It is useful when you need to fetch a list of products from your Tiny ERP system, for example, to synchronize product data with another system, generate reports, or perform bulk operations.
Typical use cases include:
- Retrieving all active products with pagination support.
- Searching products by partial or full name, product code, or GTIN barcode.
- Filtering products by creation or modification dates.
- Limiting the number of returned results and skipping a certain number of entries (offset).
Properties
| Name | Meaning |
|---|---|
| Code | Search by exact product code (string). |
| Creation Date | Filter products created on a specific date/time (dateTime). |
| GTIN | Search by GTIN barcode (string). |
| Limit | Maximum number of results to return (number, minimum 1). Defaults to 50. |
| Modification Date | Filter products modified on a specific date/time (dateTime). |
| Name | Search by partial or complete product name (string). |
| Offset | Number of results to skip (number, minimum 0). Defaults to 0. |
| Status | Product status filter; options are "Active" or "Inactive". Defaults to "Active". |
Output
The output is an array of JSON objects representing the products retrieved from the Tiny ERP API. Each item corresponds to one product record with all its details as provided by the API.
Example structure (simplified):
[
{
"id": 123,
"nome": "Product Name",
"codigo": "P001",
"gtin": "7891234567890",
"situacao": "A",
"dataCriacao": "2023-01-01T12:00:00Z",
"dataAlteracao": "2023-02-01T12:00:00Z",
...
},
...
]
No binary data is output by this operation.
Dependencies
- Requires an API authentication credential configured in n8n to access the Tiny ERP API.
- The node uses HTTP requests to communicate with the 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 results without proper limits might lead to timeouts or large payloads.
Error messages:
"The operation "getAll" is not supported!"— This would indicate a misconfiguration but should not occur if using the correct operation."The resource "product" is not supported!"— Indicates the resource parameter is incorrect.- API errors returned from Tiny ERP will be passed through; check the error message for details such as invalid parameters or permission issues.
Resolution tips:
- Verify API credentials and permissions.
- Ensure date/time fields are correctly formatted.
- Use reasonable limits and offsets to paginate results.
Links and References
- Tiny ERP API Documentation (official API docs, for detailed endpoint info)
- n8n Documentation (for general usage of custom nodes and credentials)