LEDGERS icon

LEDGERS

Interact with LEDGERS API
Join our community

Actions34

Overview

This node allows users to create a new contact record in the LEDGERS system via its API. It is useful for automating the addition of contacts with detailed information such as addresses, currency preferences, tax details, and opening balances. Typical scenarios include CRM automation, syncing contact data from other systems, or bulk importing contacts.

For example, you can use this node to add a new customer with billing and shipping addresses, specify their preferred currency, provide tax numbers, and set initial receivables or payables, all in one operation.

Properties

Name Meaning
Contact Name The full name of the contact to be created (required).
Additional Fields A collection of optional fields to enrich the contact's profile:
- Billing Address One or more billing addresses including address lines, city, country, email, mobile, postal code, state, and tax number.
- Currency The preferred currency for the contact. Options include a wide range of international currencies such as USD, EUR, INR, GBP, etc.
- Shipping Address One or more shipping addresses similar in structure to billing addresses.
- Email Contact's email address.
- Mobile Country Code Country dialing code for the mobile number. Includes many country codes like +91 (India), +1 (USA/Canada), +44 (UK), etc.
- Mobile Contact's mobile phone number without country code.
- Tax Number Tax identification number for the contact.
- Opening Customer Receivable Opening balance amount and financial year for customer receivables.
- Opening Supplier Payable Opening balance amount and financial year for supplier payables.
- PAN (India Only) Permanent Account Number specific to India.
- Business Name The business or company name associated with the contact.
- Status The status of the contact, either "Active" or "Inactive".

Output

The node outputs JSON data representing the newly created contact record as returned by the LEDGERS API. This typically includes the contact's unique identifier, entered details, and any metadata provided by the API response.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the LEDGERS API.
  • Needs valid user credentials (email and password) for login to obtain an API token.
  • The node makes HTTP requests to the LEDGERS API endpoints.
  • Proper configuration of the API URL and credentials in n8n is necessary.

Troubleshooting

  • Authentication Failures: Errors indicating failed login usually mean incorrect API key, email, or password. Verify credentials and API URL.
  • Invalid Input Data: Missing required fields like Contact Name will cause errors. Ensure all mandatory properties are provided.
  • API Response Errors: If the API returns unexpected data or error messages, check network connectivity and API service status.
  • Country Code Mismatch: Selecting an incorrect mobile country code may lead to invalid phone number formatting.
  • Address Format Issues: Providing incomplete or malformed address details might cause validation errors on the API side.

To resolve these issues:

  • Double-check all input parameters.
  • Confirm API credentials and endpoint URLs.
  • Review API documentation for field requirements.
  • Use the node's error messages to identify missing or incorrect data.

Links and References

Discussion