Fatture in Cloud icon

Fatture in Cloud

Interact with Fatture in Cloud API

Actions67

Overview

This node integrates with the "Fatture in Cloud" API, specifically allowing users to create archive documents within their account. Archive documents typically represent stored or historical records related to a company’s operations, such as scanned invoices, receipts, or other important files that need to be archived for compliance or record-keeping.

A common use case is automating the archival of documents received or generated by a company, ensuring they are properly categorized and timestamped without manual intervention. For example, after processing an invoice, a user can automatically create an archive document with relevant metadata and attach the original file via a token.

Properties

Name Meaning
Company ID The numeric identifier of the company under which the archive document will be created.
Date The date associated with the archive document (e.g., creation or document date).
Category The category or type of the archive document (e.g., invoice, receipt, contract).
Description A textual description providing details about the archive document.
Attachment Token A secure token representing the attachment/document to be linked with the archive entry.

Output

The node outputs JSON data representing the result of the archive document creation operation. This typically includes details of the newly created archive document such as its ID, status, and any metadata returned by the API.

If the node supports binary data output (not explicitly shown here), it would relate to the attached document content; however, based on the provided code and properties, the main output is structured JSON confirming the creation and details of the archive document.

Dependencies

  • Requires an active connection to the Fatture in Cloud API using OAuth2 authentication.
  • The node depends on the presence of a valid API credential configured in n8n.
  • The attachmentToken property suggests that attachments must be uploaded or referenced beforehand, likely requiring separate handling or API calls to generate this token.

Troubleshooting

  • Common Issues:

    • Invalid or missing Company ID can cause failures in creating the archive document.
    • Incorrect or expired attachmentToken may lead to errors attaching the document.
    • Network or authentication issues with the Fatture in Cloud API can interrupt execution.

  • Error Messages:

    • Errors from the API are caught and presented with detailed messages including HTTP status and error descriptions.
    • If the node is set to continue on failure, errors are returned as part of the output JSON with an error field.
    • Typical error resolution involves verifying credentials, ensuring correct input parameters, and checking the validity of the attachment token.

Links and References

Discussion