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 to perform operations related to issued documents. Specifically, the Join operation under the Issued Document resource allows users to combine multiple issued documents into a single new document of a specified type. This is useful for consolidating related documents such as delivery notes, orders, quotes, or work reports into one comprehensive document.
Practical scenarios include:
- Merging several delivery notes into one consolidated delivery note for easier tracking.
- Combining multiple orders into a single order document for streamlined processing.
- Joining various quotes or work reports to create summary documents for clients or internal use.
Properties
| Name | Meaning |
|---|---|
| Company ID | The numeric identifier of the company under which the documents exist and will be joined. |
| Document IDs | A comma-separated string listing the IDs of the documents to join together. |
| Group Documents | Numeric parameter that may control grouping behavior when joining documents (exact usage depends on API). |
| Join Type | The type of document to create from the join operation. Options: |
| - Delivery Notes | |
| - Orders | |
| - Quotes | |
| - Work Reports |
Output
The node outputs JSON data representing the result of the join operation. This typically includes details about the newly created joined document, such as its ID, status, and metadata returned by the Fatture in Cloud API.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Fatture in Cloud API via an OAuth2-based API key credential.
- The node depends on the Fatture in Cloud service being accessible and the provided company and document IDs being valid within that service.
Troubleshooting
Common issues:
- Invalid or missing Company ID or Document IDs can cause errors.
- Providing document IDs that do not belong to the specified company or are invalid will result in API errors.
- Network or authentication failures due to expired or incorrect API credentials.
Error messages:
- Errors returned from 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 included in the output JSON with an
errorfield. - To resolve errors, verify the correctness of input parameters, ensure API credentials are valid, and check network connectivity.
Links and References
- Fatture in Cloud Official API Documentation (for detailed API capabilities and parameters)
- n8n documentation on Creating Custom Nodes