Actions28
- Product Actions
- Product Stock Actions
Overview
This node integrates with the Tiny ERP system to manage product data. Specifically, the Update Product operation allows users to modify existing product details in Tiny ERP by specifying the product ID and the fields to update. This is useful for keeping product information current, such as updating descriptions, SKUs, barcodes, or other attributes.
Practical examples include:
- Updating a product’s description or complementary description after a rebranding.
- Changing the SKU or GTIN barcode when products are repackaged.
- Modifying warranty or unit of measurement details to reflect new policies.
Properties
| Name | Meaning |
|---|---|
| Product ID | The unique identifier of the product to update. |
| Product Data | A collection of fields representing product attributes to update. Options include: |
| - Complementary Description: Additional descriptive text about the product. | |
| - Description: Main product description. | |
| - GTIN: Global Trade Item Number barcode. | |
| - NCM: Product classification code. | |
| - Observations: Any additional notes or remarks. | |
| - Origin: Numeric code indicating product origin. | |
| - SKU: Stock Keeping Unit identifier. | |
| - Type: Product type, selectable from Kit, Manufactured Product, Product with Variations, Raw Material, Simple Product. | |
| - Unit: Unit of measurement (e.g., kg, pcs). | |
| - Warranty: Warranty information string. |
Output
The output JSON confirms the success of the update operation and returns the productId of the updated product:
{
"success": true,
"productId": 123
}
This indicates that the product with the specified ID was successfully updated. No binary data is produced by this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to connect securely to the Tiny ERP API.
- Relies on the Tiny ERP REST API endpoints for product management.
- The node uses HTTP methods (
PUT) to send update requests to/produtos/{productId}endpoint.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Product ID will likely result in an error from the API.
- Omitting required fields or sending improperly formatted data in
Product Datamay cause the update to fail. - Network or authentication errors if the API credentials are missing or incorrect.
Error messages:
"The operation "update" is not supported!"— This would occur if the operation parameter is incorrectly set.- API errors related to validation or authorization will be returned from the Tiny ERP API; ensure the API key is valid and has sufficient permissions.
Resolution tips:
- Verify the Product ID exists in Tiny ERP before attempting an update.
- Double-check all input fields for correct types and required values.
- Ensure the API credentials are correctly configured and active in n8n.
Links and References
- Tiny ERP API Documentation (example link, replace with actual)
- n8n documentation on Creating Custom Nodes
- General REST API usage best practices