Actions39
- Account Actions
- Client Actions
- Document Actions
- Product Actions
- Receipt Actions
- Store Actions
- Supplier Actions
Client → Update Client
AI-generatedOverview
This node integrates with the Vendus API to update client information in a business management and invoicing system. It allows users to modify details of an existing client such as name, contact info, address, status, and custom JSON data. This is useful for keeping client records up-to-date, correcting errors, or adding new information after the client has been created.
Practical examples include:
- Updating a client's email or phone number after they provide new contact details.
- Changing the client's status from inactive to active when they resume business.
- Adding notes or external references related to the client for internal tracking.
- Modifying address information if the client moves or changes location.
Properties
| Name | Meaning |
|---|---|
| Client Name or ID | The unique identifier or name of the client to update. Can be selected from a list or specified via an expression. |
| Client Name | The updated name of the client. |
| Contact Information | Collection of contact details including: Email, Fiscal ID, Mobile number, Phone number, and Website URL. |
| Address Information | Collection of address details including: Address, City, Country (options: Angola, France, Portugal, Spain), and Postal Code. |
| Additional Options | Extra client options such as External Reference (a string), Notes (text about the client), and Status (Active or Inactive). |
| Custom JSON | A JSON object allowing arbitrary additional client data to be included. |
| Options | General options for the operation, currently includes "Enable Debug Logging" which toggles detailed debug logs for troubleshooting API calls. |
Output
The node outputs an array of JSON objects representing the response from the Vendus API after updating the client. Each item corresponds to one input item processed and contains the updated client data as returned by the API.
If debug logging is enabled, detailed logs about the request and response are generated internally but not outputted directly.
No binary data is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Vendus API.
- The base URL for the Vendus API must be configured in the credentials.
- Network access to the Vendus API endpoint is necessary.
- Optionally, enabling debug logging requires no extra setup but will produce verbose logs.
Troubleshooting
- Missing Required Parameters: If required parameters like
clientIdornameare not provided, the node throws an error indicating the missing parameter. - API Authentication Errors: Failure to authenticate due to invalid or missing API keys will cause request failures.
- Invalid URL or Routing Configuration: If the node's internal routing configuration for the resource-operation pair is missing or incorrect, it will throw an error.
- Network Issues: Connectivity problems to the Vendus API will result in request failures.
- Debug Logging: Enabling debug logging helps identify issues by providing detailed request and response information in the execution logs.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output JSON.
Links and References
- Vendus API Documentation (as referenced in the node description)
- n8n Expressions Documentation - for using expressions in parameters