Fatture in Cloud icon

Fatture in Cloud

Interact with Fatture in Cloud API

Overview

The node integrates with the Fatture in Cloud API, specifically supporting operations on various resources including E-Invoices. For the E-Invoice resource and the Get XML operation, it retrieves the XML representation of a specified issued electronic invoice document. This can optionally include any attachments associated with the invoice.

This node is useful for automating workflows that require fetching official invoice data in XML format, such as:

  • Archiving or backing up invoice XML files.
  • Sending invoice XMLs to accounting or tax software.
  • Verifying or processing invoice data programmatically.
  • Including invoice XMLs as part of automated email notifications.

Example: Automatically retrieve the XML of an issued e-invoice by its document ID and company ID, then save or forward the XML file for compliance or record-keeping purposes.

Properties

Name Meaning
Company ID The numeric identifier of the company related to the e-invoice operation.
Document ID The numeric identifier of the issued e-invoice document to retrieve.
Include Attachment Boolean flag indicating whether to include attachments within the returned XML document.

Output

The node outputs JSON data representing the result of the API call to fetch the e-invoice XML. The structure typically includes the XML content of the requested invoice document. If the "Include Attachment" option is enabled, the output may also contain embedded or linked attachment data within the XML.

If binary data (such as raw XML files or attachments) is returned by the API, it would be included accordingly, but this node primarily returns structured JSON containing the XML content.

Dependencies

  • Requires an OAuth2 API credential configured for authenticating with the Fatture in Cloud API.
  • Network access to the Fatture in Cloud service endpoint.
  • Proper permissions granted to the API key or token to access e-invoice documents.

Troubleshooting

  • Common issues:

    • Invalid or missing Company ID or Document ID parameters will cause the API call to fail.
    • Insufficient API permissions or expired credentials may result in authentication errors.
    • Requesting XML for a non-existent or unauthorized document will return an error from the API.
  • Error messages:

    • Errors from the API are captured and reported with details including status code and message.
    • Typical error messages include validation failures, authorization errors, or not found responses.
    • To resolve, verify input parameters, refresh or reconfigure credentials, and ensure the document exists and is accessible.
  • The node supports continuing execution on failure if configured, allowing partial processing of multiple items.

Links and References

Discussion