Tiny ERP Auth2 icon

Tiny ERP Auth2

Interact with Tiny ERP API v3 with OAuth2

Actions21

Produtos → Create

AI-generated

Overview

This node integrates with the Tiny ERP API v3 using OAuth2 authentication to create new product records in the ERP system. It is designed for automating product management workflows, such as adding new products with detailed attributes including pricing, stock control, taxation, and supplier information.

Common scenarios where this node is beneficial include:

  • Automatically syncing product catalogs from external systems or databases into Tiny ERP.
  • Creating complex product entries with variations, kits, and production details without manual data entry.
  • Managing inventory by defining stock parameters and suppliers programmatically.

For example, an e-commerce platform could use this node to push newly added products directly into Tiny ERP, ensuring consistent product data across sales channels and back-office systems.

Properties

Name Meaning
SKU Product SKU code (unique identifier)
Description Product description
Product Type Type of product: Kit, Product, or Service
Complementary Description Additional product description
Unit Unit of measurement
Units per Box Number of units per box
NCM Code NCM (Nomenclatura Comum do Mercosul) code
GTIN Global Trade Item Number (barcode)
Origin Product origin code (numeric)
Tax Substitution Code Tax substitution specification code
Warranty Product warranty information
Observations Additional observations
Brand ID Brand identifier (numeric)
Category ID Category identifier (numeric)
Prices Collection of prices including:
- Regular price
- Promotional price
- Cost price
Dimensions Collection of dimensions including:
- Package ID
- Package type
- Width (cm)
- Height (cm)
- Length (cm)
- Diameter (cm)
- Net Weight (kg)
- Gross Weight (kg)
Taxation Collection of taxation details including:
- Package GTIN code
- Fixed IPI tax value
- IPI tax class
SEO Collection of SEO metadata including:
- Title
- Description
- Keywords (comma-separated)
- Video URL
- URL slug
Suppliers Multiple suppliers with:
- Supplier ID
- Product code at supplier
- Whether default supplier
Stock Stock control settings including:
- Control stock (boolean)
- On demand (boolean)
- Minimum stock
- Maximum stock
- Preparation days
- Location
- Initial stock quantity
Attachments Multiple attachments with:
- URL
- External reference
Grade Product grade or variation attributes (comma-separated string)
Production Production details including:
- Products (multiple product components with ID and quantity)
- Stages (comma-separated string)
Kit Components Kit components with:
- Product ID
- Quantity
Variations Multiple product variations with:
- SKU
- GTIN
- Price
- Promotional price
- Initial stock
- Grade attributes (key:value pairs)

Output

The node outputs JSON objects representing the created product(s) as returned by the Tiny ERP API. Each output item contains a json field with the product data, which typically includes identifiers assigned by the ERP, confirmation of the saved fields, and any additional metadata returned by the API.

No binary data output is indicated.

Dependencies

  • Requires an OAuth2 API credential configured in n8n to authenticate with the Tiny ERP API v3.
  • Depends on the Tiny ERP API being accessible and properly configured for the authenticated user.
  • The node uses an internal operation factory to handle resource-specific operations; here it uses the "produtos" (products) resource with the "create" operation.

Troubleshooting

  • Unknown resource error: If the node throws an error about an unknown resource, verify that the resource name is correctly set to "produtos" and that the operation is "create".
  • Authentication failures: Ensure the OAuth2 credentials are valid and have sufficient permissions to create products in Tiny ERP.
  • Validation errors: Required fields like SKU, Description, and Product Type must be provided; missing these will cause API errors.
  • API rate limits or connectivity issues: Network problems or API throttling may cause request failures; check network connectivity and API usage limits.
  • Continue on Fail behavior: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON under an error key.

Links and References

Discussion