
Tiny ERP
Actions9
- Products Actions
- Orders Actions
- Users Actions
Overview
This node integrates with the Tiny ERP system to create new product entries. It is designed for users who want to automate adding products into their ERP database directly from n8n workflows. Typical use cases include syncing product catalogs from external sources, automating inventory setup during onboarding, or batch-creating products based on business logic.
For example, a retailer could use this node to automatically add new products received from suppliers into their ERP system, including detailed information such as pricing, stock limits, and packaging details.
Properties
| Name | Meaning |
|---|---|
| Product Code | Unique identifier code for the product (required). |
| Product Name | Name of the product (required). |
| Unit | Unit of measurement for the product (e.g., UN, KG, M) (required). |
| Price | Selling price of the product (required). |
| Origin | Product origin category: National, Foreign - Direct Import, or Foreign - Acquired in Domestic Market (required). |
| Status | Product status: Active or Inactive. |
| Type | Product type: Regular product or Service. |
| Additional Options | Collection of optional fields to provide more product details: |
| - Promotional Price: Discounted price. | |
| - NCM: Mercosur Common Nomenclature code. | |
| - GTIN/EAN: Barcode number. | |
| - Package GTIN/EAN: Barcode for the package. | |
| - Net Weight: Weight excluding packaging (kg). | |
| - Gross Weight: Weight including packaging (kg). | |
| - Minimum Stock: Minimum stock quantity threshold. | |
| - Maximum Stock: Maximum stock quantity threshold. | |
| - Cost Price: Cost price of the product. | |
| - Brand: Brand name. | |
| - Category: Product category hierarchy (use ">>" for subcategories). | |
| - Warranty: Warranty period. | |
| - CEST: Specific tax code. | |
| - Complementary Description: Additional descriptive text. | |
| - Observations: Internal notes or remarks. | |
| - Package Type: Packaging format (Box, Package, Envelope). | |
| - Package Height, Length, Width, Diameter: Dimensions of the package in centimeters. |
Output
The node outputs JSON data representing the created product(s) as returned by the Tiny ERP API. This typically includes confirmation details such as the product ID assigned by the ERP, the submitted product data, and any relevant metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Tiny ERP API.
- The user must configure an API authentication credential (such as an API key or token) within n8n to authorize requests.
- Network access to the Tiny ERP service endpoint is necessary.
Troubleshooting
- Missing Required Fields: If required properties like Product Code, Product Name, Unit, Price, or Origin are not provided, the node will likely throw validation errors. Ensure all mandatory fields are filled.
- Invalid Field Formats: Numeric fields such as Price, Promotional Price, Weights, and Stock quantities should be valid numbers formatted as strings. Incorrect formats may cause API rejections.
- API Authentication Errors: Failure to authenticate with the Tiny ERP API will result in authorization errors. Verify that the API credentials are correctly configured and have sufficient permissions.
- Unsupported Operation Error: If the node configuration specifies an unsupported operation or resource, it will throw an error indicating the operation is not supported.
- Network Issues: Connectivity problems can cause timeouts or failed requests. Check network settings and API availability.
Links and References
- Tiny ERP Official Documentation (general reference for product management)
- n8n Documentation for configuring API credentials and using nodes in workflows