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 cashbook entries for a company. Specifically, the Create operation under the Cashbook resource allows users to add new cashbook records representing financial transactions such as receipts, expenses, or movements of money.
This node is beneficial in scenarios where businesses want to automate bookkeeping tasks by programmatically adding cash flow entries into their accounting system. For example, after processing payments or expenses in other systems, this node can be used to log those transactions directly into the company's cashbook without manual entry.
Practical examples:
- Automatically recording daily sales receipts as cashbook entries.
- Logging expense reimbursements or supplier payments.
- Tracking internal fund transfers between accounts as movement entries.
Properties
| Name | Meaning |
|---|---|
| Company ID | The numeric identifier of the company for which the cashbook entry is created. |
| 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 or purpose of the cashbook entry. |
| Kind | The type of cashbook entry. Options: Receipt (money received), Expense (money spent), Movement (internal transfer). |
Output
The node outputs JSON data representing the newly created cashbook entry as returned by the Fatture in Cloud API. Each output item corresponds to one input item processed and contains the details of the created record.
If the API supports binary data related to cashbook entries (not indicated here), it would be included accordingly, but based on the provided code and properties, the output is purely JSON.
Dependencies
- Requires an active connection to the Fatture in Cloud API using OAuth2 authentication.
- The node depends on the presence of a valid API key credential configured in n8n for authentication.
- Network access to the Fatture in Cloud service endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing company ID may cause the API to reject the request.
- Incorrect date format or missing required fields like description will result in validation errors.
- Insufficient permissions or expired API tokens can lead to authentication failures.
Error messages:
- Errors from the API are caught and presented with details including status codes and error messages.
- Typical error message format:
Fatture in Cloud API Error: <error message>. - To resolve, verify all required parameters, ensure the API credentials are valid, and check network connectivity.
Continue on Fail:
- If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output.
Links and References
- Fatture in Cloud API Documentation (official API docs)
- n8n OAuth2 Credential Setup (for configuring API authentication)