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 updates an existing address for a specified contact in the system. It allows users to modify either the billing or shipping address of a contact by selecting the specific address entry and updating its fields. This is useful in scenarios where contact information changes, such as when a customer moves to a new location or updates their contact details.
Practical examples include:
- Updating the billing address of a client after they relocate.
- Correcting or adding missing details like postal code or state in the shipping address.
- Modifying optional contact details such as email or mobile number associated with an address.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact whose address is to be updated. |
| Address Type | Specifies which type of address to update; options are "Billing Address" or "Shipping Address". |
| Address Name or ID | Selects the specific address entry to update from a list or by specifying an ID via expression. |
| Update Fields | Collection of fields to update within the selected address, including: |
| - Address Line 1: Primary street address line. | |
| - Address Line 2: Secondary street address line (optional). | |
| - City: City name. | |
| - Country: Country name. | |
| - Email: Email address related to the address (optional). | |
| - Mobile: Mobile phone number (optional). | |
| - Postal Code: Postal or pin code. | |
| - State: State or province name. | |
| - TAX Number: Tax identification number. |
Output
The node outputs JSON data representing the result of the address update operation. Typically, this will include confirmation of the updated address details or the updated contact record reflecting the changes made.
If the node supports binary data output, it would generally relate to attachments or documents linked to the contact, but this operation focuses on JSON data only.
Dependencies
- Requires an API key credential and user authentication credentials (email and password) to access the external LEDGERS API.
- The node performs login requests to obtain an API token before making further API calls.
- The node depends on the LEDGERS API endpoints for contacts and addresses.
- Proper configuration of the API URL and credentials in n8n is necessary for successful execution.
Troubleshooting
- Authentication Failures: If the node throws errors about failed login or invalid credentials, verify that the API key, email, and password are correctly configured and active.
- Invalid Contact ID: Errors may occur if the provided Contact ID does not exist or is incorrect. Ensure the Contact ID is valid and corresponds to an existing contact.
- Address Selection Issues: If no addresses appear in the selection list or the specified address ID is invalid, confirm that the contact has addresses of the specified type and that the correct address is chosen.
- API Rate Limits or Downtime: Temporary failures might happen due to API rate limits or service downtime. Retrying after some time or checking API status can help.
- Missing Required Fields: Ensure all required fields, especially Contact ID and at least one field in Update Fields, are provided to avoid validation errors.
Links and References
- n8n Expressions Documentation — For using expressions in property values.
- LEDGERS API documentation (not publicly linked here) — Consult your API provider for detailed endpoint and authentication info.