Actions34
- Banking Operation (India) Actions
- Catalog Operation Actions
- Contact Operation Actions
- HRMS Operation (India) Actions
- Purchase Operation (India) Actions
- Sales Operation (India) Actions
- Tax Operation (India) Actions
Overview
This node operation allows you to add an address to an existing contact in the LEDGERS system. It supports adding billing, shipping, or both types of addresses for a specified contact by their ID. This is useful in scenarios where you need to update contact information with new or additional address details, such as when a customer moves, or you want to maintain separate billing and shipping addresses.
Practical examples:
- Adding a new shipping address for a customer who wants deliveries sent to a different location.
- Adding both billing and shipping addresses simultaneously for a new contact record update.
- Updating tax or mobile number information associated with a contact’s address.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to which the address will be added. |
| Address Type | Specifies the type of address to add. Options: Billing Address, Shipping Address, Both (Billing & Shipping). |
| Address Fields | A collection of fields describing the address details: |
| - Address Line 1: Primary street address line. | |
| - Address Line 2: Secondary street address line (optional). | |
| - City: City or location name. | |
| - Country: Country name. | |
| - Email: Email address related to this address (optional). | |
| - Mobile: Mobile phone number related to this address (optional). | |
| - Postal Code: Postal or pin code. | |
| - State: State or province name. | |
| - Tax Number: Tax identification number associated with the address. |
Output
The node outputs JSON data representing the result of the address addition operation. Typically, this would include confirmation of the updated contact record or the newly added address details. The exact structure depends on the API response from the LEDGERS backend but generally includes status and updated contact information.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential and user authentication credentials (email and password) for the LEDGERS API.
- The node performs login requests to obtain an API token before making further API calls.
- The API URL endpoint must be configured correctly in the credentials.
- Network access to the LEDGERS API service is required.
Troubleshooting
- Authentication failures: If the node throws errors about failed login or invalid credentials, verify that the API key, email, and password are correct and have sufficient permissions.
- Invalid Contact ID: Ensure the Contact ID provided exists in the system; otherwise, the API may return errors or no data.
- Missing required fields: The Contact ID and at least one address field (like Address Line 1, City, Country, Postal Code) should be provided; missing these may cause the API to reject the request.
- API endpoint issues: Confirm the API URL is reachable and correct, especially if using different environments (production vs development).
- Network errors: Check network connectivity and firewall settings if requests time out or fail.
Links and References
- LEDGERS API documentation (not included here, but typically available from the service provider)
- n8n documentation on creating and configuring custom nodes and credentials
This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.