LEDGERS icon

LEDGERS

Interact with LEDGERS API
Join our community

Actions34

Overview

This node operation "Add Variant (Existing Catalog)" allows users to add a new product variant to an existing catalog in the connected system. It is useful for e-commerce, inventory management, or product catalog systems where products have multiple variants differing by attributes such as size, color, or price.

Typical scenarios include:

  • Adding a new size or color option to an existing product.
  • Introducing a new pricing tier or SKU for a product variant.
  • Managing product catalogs dynamically without manual intervention.

For example, if you have a T-shirt product in your catalog, you can use this node to add a variant like "Large Blue T-shirt" with its own price and SKU.

Properties

Name Meaning
Catalog ID The unique identifier of the catalog to which the variant will be added. This is required to specify the target catalog.
Variant Name The name of the new variant being added (e.g., "Large Blue"). Required field.
Price The price of the variant. This should be provided as a string representing the amount. Required field.
Additional Fields A collection of optional fields to provide more details about the variant:
- Currency The currency code for the price. Options include many global currencies such as USD, EUR, INR, GBP, JPY, etc. Default is INR.
- Non-Taxable Numeric value indicating the non-taxable amount for the variant, if any.
- SKU ID The stock keeping unit identifier for the variant, used for inventory tracking. Optional string.
- Tax Type Specifies whether the price is "Inclusive of Tax" or "Exclusive of Tax". Default is "Inclusive of Tax".
- Variant Description A textual description of the variant, providing additional information. Optional string.

Output

The node outputs JSON data representing the result of the add variant operation. Typically, this includes confirmation of the variant addition, variant details, or error messages if the operation failed.

No binary data output is indicated.

Dependencies

  • Requires an API key credential and user authentication credentials (email and password) to connect to the external LEDGERS API service.
  • The node performs HTTP requests to the LEDGERS API endpoints to authenticate and then add the variant to the specified catalog.
  • Proper configuration of the API URL and credentials within n8n is necessary for successful execution.

Troubleshooting

  • Authentication Failures: If the node throws errors related to authentication, verify that the API key, email, and password credentials are correct and active.
  • Invalid Catalog ID: Ensure the Catalog ID exists and is accessible by the authenticated user; otherwise, the variant cannot be added.
  • Missing Required Fields: The node requires Catalog ID, Variant Name, and Price. Omitting these will cause errors.
  • Currency Issues: Use one of the supported currency codes from the options list; unsupported or misspelled codes may cause failures.
  • API Errors: Network issues or API downtime can cause request failures. Check connectivity and API status.
  • Error Messages: The node may throw warnings or errors with messages like "Authentication failed. Check your credentials." or "Failed to login." These indicate credential or connectivity problems.

Links and References

This summary is based solely on static analysis of the provided source code and property definitions.

Discussion