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 integrates with the "Fatture in Cloud" API, specifically allowing users to interact with issued documents within their account. The "Get Many" operation under the "Issued Document" resource fetches multiple issued documents for a specified company. This is useful for scenarios such as retrieving invoices, receipts, or other issued financial documents in bulk for reporting, auditing, or synchronization with other systems.
Practical examples include:
- Fetching all issued invoices for a company to generate a financial report.
- Retrieving a limited number of recent issued documents for quick review or processing.
- Integrating issued document data into an ERP or accounting system.
Properties
| Name | Meaning |
|---|---|
| Company ID | The numeric identifier of the company whose issued documents you want to retrieve. |
| Return All | Boolean option to return all issued documents available or limit the number of results. |
| Limit | Maximum number of issued documents to return when "Return All" is set to false. |
Output
The node outputs an array of JSON objects representing issued documents retrieved from the API. Each object contains the details of a single issued document, such as invoice number, date, client information, amounts, and status (the exact fields depend on the API response structure).
If binary data were involved (e.g., PDF copies of documents), it would be included in a separate binary property, but this operation focuses on JSON data output only.
Dependencies
- Requires an OAuth2 API credential configured for authenticating with the Fatture in Cloud API.
- The node depends on the external Fatture in Cloud service being accessible and the user having appropriate permissions to access issued documents for the specified company.
Troubleshooting
Common issues:
- Invalid or missing company ID will cause the API call to fail.
- Insufficient permissions or expired authentication tokens can result in authorization errors.
- Network connectivity problems may prevent successful API communication.
Error messages:
- Errors returned by the API are captured and presented with details including HTTP status and error message.
- If the node is set to continue on failure, errors for individual items are returned as JSON objects with an
errorfield. - To resolve errors, verify the company ID, check API credentials, and ensure network connectivity.