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 archive documents within a company’s account. Specifically, the Update Archive Document operation allows users to modify existing archived documents by specifying their document ID and updating fields such as date, category, description, and attachment token.
This node is beneficial for automating document management workflows where archived records need to be kept current without manual intervention. For example, an accounting team could automatically update metadata or attachments of archived invoices or receipts after receiving additional information or corrections.
Practical examples:
- Updating the category or description of an archived invoice after reclassification.
- Changing the date of an archived receipt to reflect the actual transaction date.
- Adding or refreshing an attachment token to link new supporting documents.
Properties
| Name | Meaning |
|---|---|
| Company ID | The numeric identifier of the company under which the archive document exists. |
| Document ID | The numeric identifier of the specific archive document to update. |
| Date | The date associated with the archive document (e.g., invoice date). |
| Category | The category classification of the archive document (e.g., Invoice, Receipt). |
| Description | A textual description providing details about the archive document. |
| Attachment Token | A secure token string used to attach or update a document file related to the archive. |
Output
The node outputs JSON data representing the updated archive document as returned by the Fatture in Cloud API. This typically includes all relevant fields of the archive document after the update, such as IDs, dates, categories, descriptions, and any metadata.
If the operation involves binary data (e.g., document attachments), the node would handle it accordingly, but based on the provided code and properties, the output focuses on JSON metadata updates rather than raw binary content.
Dependencies
- Requires an active connection to the Fatture in Cloud API via OAuth2 authentication.
- The node depends on the user having valid credentials configured in n8n for accessing the Fatture in Cloud service.
- No other external dependencies are indicated beyond the bundled modules handling different resource types.
Troubleshooting
Common issues:
- Invalid or missing Company ID or Document ID will cause the API to reject the update request.
- Incorrect attachment tokens may result in failure to associate files properly.
- Network or authentication errors if the OAuth2 token is expired or invalid.
Error messages:
Unknown resource: Occurs if the specified resource name does not match supported resources.Fatture in Cloud API Error: Generic error wrapper that includes status codes and detailed API response messages.
Resolutions:
- Verify that all required parameters (Company ID, Document ID, Date, Category, Description) are correctly set.
- Ensure the OAuth2 credentials are valid and refreshed.
- Check the attachment token format and validity if attachments are involved.
- Use the node’s “Continue On Fail” option to handle partial failures gracefully during batch operations.