LEDGERS icon

LEDGERS

Interact with LEDGERS API

Overview

This node allows users to create a new catalog entry in an external accounting or ERP system via its API. It is designed for managing product or service catalogs, including details such as pricing, tax information, units, and descriptions.

Typical use cases include:

  • Automating the addition of new products or services into a sales or purchase catalog.
  • Integrating with accounting systems to keep product listings synchronized.
  • Managing inventory items with detailed tax and pricing configurations.

For example, a business could use this node to automatically add newly developed products into their sales catalog with correct pricing, tax rates, and unit measures, streamlining their sales process.

Properties

Name Meaning
Catalog Name The name of the catalog item to be created.
Price The price of the catalog item.
Catalog Type The type of catalog: either "Sales" or "Purchase".
Item Type The type of item: either "Goods" or "Services".
Additional Fields A collection of optional fields to provide more details about the catalog item:
- Currency The currency code for the price (e.g., USD, INR, EUR).
- Price Type Whether the price is "Inclusive of Tax" or "Exclusive of Tax".
- Tax Rate The applicable tax rate or category (e.g., 5%, 18%, Exempted Supply).
- Non-Taxable Amount that is non-taxable within the price.
- Units Unit of measurement for the item (e.g., PCS-PIECES, KGS-KILOGRAMS, LTR-LITRES).
- Product Description A textual description of the product or service.
- HSN/SAC Code Harmonized System of Nomenclature (HSN) or Service Accounting Code (SAC) used for tax classification.
- Expense Name or ID An expense account identifier or name linked to the catalog item, selectable from a list loaded dynamically.
- Cess Type Type of cess applied: "Percentage" or "Flat Value".
- Cess Value Numeric value of the cess applied.

Output

The node outputs JSON data representing the response from the external API after creating the catalog item. This typically includes confirmation details such as the created catalog's ID, status, and any metadata returned by the API.

No binary data output is indicated.

Dependencies

  • Requires an API key credential and user authentication (email and password) to access the external API.
  • The node performs login requests to obtain an API token before making catalog creation calls.
  • The API URL endpoint must be configured appropriately.
  • Uses HTTP POST requests with JSON payloads to interact with the external service.

Troubleshooting

  • Authentication Failures: If login fails, the node throws an error indicating authentication failure. Verify that the API key, email, and password credentials are correct and have sufficient permissions.
  • Invalid Input Data: Missing required fields like Catalog Name or Price will likely cause errors. Ensure all mandatory properties are provided.
  • API Response Errors: If the external API returns unexpected data or errors, check network connectivity and API endpoint correctness.
  • Dynamic Option Loading Failures: Some properties load options dynamically (e.g., Expense Name or ID). If these fail, it may be due to authentication issues or API changes.

Links and References

  • No direct external links are embedded in the source code, but typical references would include:
    • The external API documentation for catalog management.
    • n8n documentation on creating custom nodes and using credentials.
    • Tax codes and HSN/SAC code references relevant to the user's country or region.

Discussion