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
This node interacts with the "Fatture in Cloud" API to list receipts associated with a specified company. It allows users to retrieve paginated lists of receipts, optionally filtered and sorted according to various criteria. This is useful for automating financial workflows, accounting tasks, or integrating receipt data into other systems.
Practical examples include:
- Fetching all receipts for a company to generate reports.
- Filtering receipts by search queries or specific fields to analyze spending.
- Paginating through large sets of receipts to process them in batches.
Properties
| Name | Meaning |
|---|---|
| Company ID | The numeric identifier of the company whose receipts you want to list. |
| Filter Options | A collection of optional filters and parameters to refine the list results: |
| - Fields | Comma-separated list of specific receipt fields to include in the response. |
| - Fieldset | Choose between "Basic" (minimal info) or "Detailed" (full info) fieldsets for the response. |
| - Page | The page number to retrieve for paginated results (default is 1). |
| - Per Page | Number of receipts per page to return (default is 50). |
| - Query | Search query string to filter receipts based on matching text. |
| - Sort | String defining the sort order of the results (e.g., by date or amount). |
Note: Some filter options like "Receipt Type" and "Year" are available only for other operations and not applicable here.
Output
The node outputs an array of JSON objects representing receipts. Each object contains receipt data fields as requested via the "Fields" or "Fieldset" input properties. The structure typically includes identifiers, dates, amounts, and other relevant receipt details depending on the chosen fieldset.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Fatture in Cloud API using OAuth2 authentication.
- The node depends on the appropriate API credentials configured in n8n.
- Network access to the Fatture in Cloud service endpoint is necessary.
Troubleshooting
Common Issues:
- Invalid or missing Company ID will cause the API call to fail.
- Incorrect pagination parameters may result in empty responses.
- Using unsupported field names in the "Fields" property can lead to errors or incomplete data.
- Network or authentication failures will prevent data retrieval.
Error Messages:
- Errors from the API are caught and reported with messages including status codes and error details.
- Typical error message format:
Fatture in Cloud API Error: <error message> - To resolve, verify API credentials, ensure correct company ID, and check network connectivity.
- If "continue on fail" is enabled, errors for individual items will be returned as error objects instead of stopping execution.
Links and References
This summary is based solely on static analysis of the provided source code and input property definitions.