Fatture in Cloud icon

Fatture in Cloud

Interact with Fatture in Cloud API

Actions67

Overview

This node interacts with the "Fatture in Cloud" API, specifically to manage received documents among other resources. The Get Totals operation for the Received Document resource retrieves summary totals related to a specific received document within a company.

Typical use cases include:

  • Fetching financial summary data (such as total amounts, taxes, or other aggregated values) for a particular received invoice or bill.
  • Automating accounting workflows by programmatically obtaining document totals for reconciliation or reporting.
  • Integrating with other systems that require up-to-date totals of received documents without manual lookup.

For example, an accountant could use this node to automatically pull totals from received invoices to update their internal bookkeeping system.

Properties

Name Meaning
Company ID The numeric identifier of the company under which the received document exists.
Document ID The numeric identifier of the specific received document for which totals are retrieved.

Output

The output is a JSON array where each item corresponds to the result of the executed operation on an input item.

  • The json field contains the totals data returned by the Fatture in Cloud API for the specified received document.
  • The exact structure depends on the API response but typically includes fields such as total amounts, tax breakdowns, and other financial summary information related to the received document.
  • This node does not output binary data.

Dependencies

  • Requires an active connection to the Fatture in Cloud API using OAuth2 authentication credentials configured in n8n.
  • The node depends on the external Fatture in Cloud service being available and accessible.
  • Proper permissions and valid company/document IDs must be provided to successfully retrieve totals.

Troubleshooting

  • Common issues:

    • Invalid or missing Company ID or Document ID will cause errors.
    • Expired or misconfigured API credentials can lead to authentication failures.
    • Network connectivity problems may prevent reaching the Fatture in Cloud API.
    • If the specified document does not exist or is inaccessible, the API will return an error.

  • Error messages:

    • Errors from the API are caught and reported with details including status code and message.
    • Typical error messages include validation errors, unauthorized access, or not found errors.
    • To resolve, verify input parameters, check API credentials, and ensure the document exists in the specified company.

  • The node supports continuing on failure if enabled, allowing partial processing of multiple items.

Links and References

Discussion