Actions67
- Archive Document Actions
- Cashbook Actions
- Client Actions
- Company Actions
- E-Invoice Actions
- Email Actions
- Info Actions
- Issued Document Actions
- Product Actions
- Receipt Actions
- Received Document Actions
- Setting Actions
- Supplier Actions
- Tax (F24) Actions
- Webhook Actions
Overview
The node integrates with the "Fatture in Cloud" API to manage client data within a company. Specifically, the Client - Update operation allows users to update existing client information by specifying the company and client IDs along with new client details. This is useful for keeping client records current, such as updating contact information, addresses, or tax details.
Practical examples include:
- Updating a client's address after they move.
- Changing the contact person or email for billing purposes.
- Modifying tax codes or VAT numbers when clients' fiscal details change.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company under which the client exists. |
| Client ID | The unique identifier of the client to be updated. |
| Client Name | The new or updated name of the client. |
| Additional Fields | Optional extra client details that can be updated, including: |
| - Address City, Extra, Postal Code, Province, Street | |
| - Certified Email (PEC) | |
| - Code | |
| - Contact Person | |
| - Country (default "Italia") | |
| - E-Invoice (boolean indicating if client uses electronic invoicing) | |
| - Electronic Invoice Code | |
| - Fax | |
| - First Name, Last Name (for person type clients) | |
| - Notes | |
| - Phone | |
| - Tax Code | |
| - Type (options: Company, Person) | |
| - VAT Number |
Output
The node outputs an array of JSON objects representing the updated client data returned from the Fatture in Cloud API. Each item corresponds to one input item processed and contains the updated client details as confirmed by the API.
If an error occurs during processing, and the node is configured to continue on failure, the output will include an error object describing the issue for the respective item.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Fatture in Cloud API via OAuth2 authentication.
- The node depends on proper configuration of credentials providing access tokens for the API.
- Network connectivity to the Fatture in Cloud service is necessary.
Troubleshooting
Common issues:
- Invalid or expired API credentials causing authentication failures.
- Incorrect Company ID or Client ID leading to "not found" errors.
- Missing required fields like Client Name or IDs.
- Validation errors if field formats do not meet API requirements (e.g., invalid email format).
Error messages:
- Errors returned from the API are captured and presented with status codes and detailed messages.
- Typical error message format:
Fatture in Cloud API Error: <error message>. - To resolve, verify credentials, ensure IDs exist, and validate all input fields before execution.