Fatture in Cloud icon

Fatture in Cloud

Interact with Fatture in Cloud API

Overview

The node interacts with the "Fatture in Cloud" API, specifically providing functionality to transform issued documents from one type to another. This transformation operation is useful when you need to convert an existing document (such as an invoice or quote) into a different document type (like a credit note or delivery note) within the same company context.

Common scenarios include:

  • Converting an invoice into a credit note to issue a refund.
  • Transforming a quote into an order once it is accepted.
  • Generating a proforma invoice from an order for preliminary billing.

This node automates these transformations, saving manual effort and ensuring consistency in document handling.

Properties

Name Meaning
Company ID The numeric identifier of the company under which the document exists and will be transformed.
Transform to Type The target document type to transform the original document into. Options:
- Credit Note
- Delivery Note
- Invoice
- Order
- Proforma
- Quote
E-Invoice Boolean flag indicating whether to enable e-invoice features on the transformed document.
Keep Copy Boolean flag indicating whether to keep a copy of the original document after transformation.
Original Document ID The numeric identifier of the original issued document that will be transformed.

Output

The node outputs JSON data representing the result of the transformation operation. This typically includes details of the newly created document after transformation, such as its ID, type, status, and other relevant metadata returned by the Fatture in Cloud API.

If the operation fails, the output may contain an error object describing the failure.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the Fatture in Cloud API via an OAuth2-based API key credential.
  • The node depends on the Fatture in Cloud service being accessible and the user having appropriate permissions to perform document transformations.
  • No additional environment variables are required beyond the configured API authentication.

Troubleshooting

  • Common Issues:

    • Invalid or missing company ID or original document ID can cause failures.
    • Attempting to transform a document to an unsupported type or invalid state may result in API errors.
    • Network connectivity issues or expired API tokens can interrupt the operation.
  • Error Messages:

    • Errors returned from the API are captured and presented with details including HTTP status and error messages.
    • Typical error message format: Fatture in Cloud API Error: <error message>.
    • To resolve, verify input parameters, ensure valid credentials, and check API service status.
  • Continue on Fail:

    • If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output.

Links and References

Discussion