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 "Cashbook" resource of the Fatture in Cloud API, specifically supporting the List operation. It retrieves cashbook entries for a specified company, optionally filtered by date range, year, and cash flow direction (in, out, or all). This is useful for financial reporting, auditing, or bookkeeping automation where you need to fetch and process cash flow records programmatically.
Practical examples:
- Automatically retrieving all cashbook entries for the current fiscal year to generate monthly cash flow reports.
- Filtering cashbook entries to only show incoming payments within a specific date range.
- Integrating cashbook data into an accounting dashboard or ERP system.
Properties
| Name | Meaning |
|---|---|
| Company ID | The numeric identifier of the company whose cashbook entries are to be listed. |
| Additional Fields | Optional filters to refine the list of cashbook entries: |
| - Date From | Start date to filter entries from (defaults to start of current year if not set). |
| - Date To | End date to filter entries up to this date. |
| - Year | Numeric year to filter entries by (default is 2025). |
| - Type | Filter by cash flow direction; options are: All, In (incoming), Out (outgoing). |
Output
The node outputs an array of JSON objects representing cashbook entries matching the query parameters. Each object corresponds to a single cashbook record retrieved from the API.
If binary data were involved, it would be summarized here, but this node deals exclusively with JSON data representing financial entries.
Dependencies
- Requires an API authentication token credential configured in n8n to access the Fatture in Cloud API.
- Relies on the Fatture in Cloud API being accessible and the provided company ID being valid.
- No additional external dependencies beyond the API and n8n's HTTP request capabilities.
Troubleshooting
Common issues:
- Invalid or missing company ID will cause the API to reject the request.
- Incorrect date formats or invalid date ranges may result in empty results or errors.
- Network connectivity problems or expired API tokens can cause authentication failures.
Error messages:
"Unknown resource: cashbook"— indicates the resource parameter was not recognized; ensure "cashbook" is selected."Fatture in Cloud API Error: <message>"— generic API error; check the detailed status and message for specifics.- Validation errors returned by the API often include details about which input parameter was incorrect.
Resolution tips:
- Verify that the company ID exists and is correct.
- Use valid ISO date strings for date filters.
- Ensure the API credentials are correctly set up and have sufficient permissions.
- Enable "Continue On Fail" in the node settings to handle partial failures gracefully.
Links and References
- Fatture in Cloud API Documentation — official API reference for understanding available endpoints and parameters.
- n8n Documentation — general guidance on using credentials and handling API nodes in n8n.