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 interacts with the "Fatture in Cloud" API, specifically allowing operations on various resources including Cashbook entries. For the Cashbook Update operation, it updates an existing cashbook entry identified by a Document ID within a specified company. This is useful for maintaining accurate financial records by modifying details such as date, amounts, description, and type of cash flow.
Practical scenarios include:
- Correcting or updating cash inflow/outflow entries after initial creation.
- Adjusting descriptions or dates to reflect accurate transaction details.
- Changing the kind of cashbook entry (e.g., from receipt to expense) to properly categorize transactions.
Properties
| Name | Meaning |
|---|---|
| Company ID | The numeric identifier of the company where the cashbook entry exists. |
| Document ID | The unique string identifier of the cashbook entry to update. |
| Date | The date and time of the cashbook entry. |
| Amount In | The amount of money coming into the company (positive cash flow). |
| Amount Out | The amount of money going out of the company (negative cash flow). |
| Description | A textual description explaining the nature of the cashbook entry. |
| Kind | The category/type of the cashbook entry. Options: Receipt, Expense, Movement. |
Output
The node outputs JSON data representing the updated cashbook entry as returned by the Fatture in Cloud API. Each output item corresponds to one input item processed and contains the updated entry's details.
If errors occur during execution, and if the node is configured to continue on failure, the output will include error objects describing the issue per item.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token credential for Fatture in Cloud.
- Network access to the Fatture in Cloud API endpoint.
- Proper configuration of the node’s credentials within n8n to authenticate requests.
Troubleshooting
Common Issues:
- Invalid or missing Company ID or Document ID will cause the API to reject the request.
- Incorrect date format or missing required fields like Description may result in validation errors.
- Insufficient permissions or expired API tokens can lead to authorization failures.
Error Messages:
- Errors returned from the API are captured and presented with status codes and messages.
- Typical error message format:
Fatture in Cloud API Error: <error message>. - To resolve, verify that all required parameters are correctly set, the API token is valid, and the referenced document exists.