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 various resources such as archive documents, companies, clients, issued documents, and more. For the Archive Document - Get operation, it retrieves a specific archived document from the user's Fatture in Cloud account.
Typical use cases include:
- Fetching archived invoices or documents for review or processing.
- Automating retrieval of historical financial documents for reporting or compliance.
- Integrating archived document data into other workflows or systems.
For example, a user might configure this node to get an archived invoice by specifying the company ID and the document ID, then use the retrieved data downstream for generating reports or sending notifications.
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 retrieve. |
Output
The node outputs JSON data representing the requested archive document's details as returned by the Fatture in Cloud API. This typically includes metadata and content fields relevant to the archived document.
If the node supports binary data output (not explicitly shown here), it would represent the actual file or attachment of the archive document, such as a PDF or image.
Dependencies
- Requires an API authentication token credential configured in n8n to access the Fatture in Cloud API.
- Depends on the external Fatture in Cloud service being available and accessible.
- No additional environment variables are indicated as necessary beyond the API credential.
Troubleshooting
Common issues:
- Invalid or missing company ID or document ID parameters will cause the API call to fail.
- Network connectivity problems or incorrect API credentials can result in authentication errors.
- Requesting a non-existent document ID may return a "not found" error.
Error messages:
- Errors from the API are caught and presented with details including status code and message.
- If
continueOnFailis enabled, errors for individual items are returned as JSON objects containing error information instead of stopping execution. - Typical error descriptions include validation failures, unauthorized access, or resource not found.
Resolution tips:
- Verify that the company ID and document ID are correct and exist in the Fatture in Cloud account.
- Ensure the API credential is valid and has sufficient permissions.
- Check network connectivity and API endpoint availability.
Links and References
- Fatture in Cloud API Documentation (official API docs)
- n8n documentation on creating custom nodes for further customization guidance