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, a platform for managing invoicing and accounting documents. Specifically, the Issued Document - Get operation retrieves detailed information about a particular issued document within a specified company.
Typical use cases include:
- Fetching invoice details to display or process them further in an automation workflow.
- Retrieving issued document data for reporting or auditing purposes.
- Integrating issued document information into other systems such as CRMs or ERPs.
For example, you might use this node to get the details of an invoice by providing the company ID and the document ID, then use that data to send a notification email or update a database record.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique numeric identifier of the company under which the issued document exists. |
| Document ID | The unique numeric identifier of the specific issued document (e.g., invoice) to retrieve. |
Output
The node outputs JSON data representing the issued document's details as returned by the Fatture in Cloud API. This typically includes fields such as document number, date, client information, amounts, status, and line items.
If the node supports binary data output (not explicitly shown here), it would represent attachments or PDF versions of the document, but this is not indicated in the provided code snippet.
Dependencies
- Requires an API authentication token credential configured in n8n to access the Fatture in Cloud API.
- Depends on the
IssuedDocumentsModuleinternal class to handle the API request for issued documents. - No additional external dependencies are indicated beyond the API connection.
Troubleshooting
Common issues:
- Invalid or missing Company ID or Document ID will cause the API call to fail.
- Authentication errors if the API token/credential is invalid or expired.
- Network or API downtime can result in request failures.
Error messages:
- Errors from the API are caught and wrapped with messages like
Fatture in Cloud API Error: <error message>. - The node provides detailed error descriptions including HTTP status codes and response data.
- If "Continue On Fail" is enabled, errors for individual items will be returned as JSON objects with an
errorfield instead of stopping execution.
- Errors from the API are caught and wrapped with messages like
Resolution tips:
- Verify that the Company ID and Document ID are correct and exist in your Fatture in Cloud account.
- Ensure the API credentials are valid and have sufficient permissions.
- Check network connectivity and API service status.
- Use the detailed error messages to identify and fix issues.
Links and References
- Fatture in Cloud Official Website
- Fatture in Cloud API Documentation (for detailed API endpoints and data structures)
- n8n Documentation on Creating Custom Nodes