Fatture in Cloud icon

Fatture in Cloud

Interact with Fatture in Cloud API

Overview

This node integrates with the Fatture in Cloud API to manage various accounting and business resources. Specifically, for the Cashbook - Delete operation, it allows users to delete a cashbook entry identified by its document ID within a specified company.

Typical use cases include automating bookkeeping tasks such as removing outdated or incorrect cashbook entries directly from workflows, ensuring your financial records stay accurate without manual intervention.

For example, you might use this node to automatically delete a cashbook record when a related transaction is voided or canceled in another system.

Properties

Name Meaning
Company ID The numeric identifier of the company under which the cashbook entry exists.
Document ID The unique string identifier of the cashbook entry to be deleted.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide error details if it failed.

  • The output json field contains an array of objects reflecting the API response.
  • If the operation fails and "Continue On Fail" is enabled, the output includes an error object describing the failure.
  • This node does not output binary data.

Dependencies

  • Requires an active connection to the Fatture in Cloud API using OAuth2 authentication (an API key credential).
  • The node depends on the internal Cashbook module that handles API requests related to cashbook entries.
  • Proper configuration of credentials in n8n is necessary to authenticate API calls.

Troubleshooting

  • Common issues:

    • Invalid or missing Company ID or Document ID parameters will cause the API call to fail.
    • Network or authentication errors may prevent successful communication with the Fatture in Cloud API.
    • Attempting to delete a non-existent cashbook entry will result in an error response.
  • Error messages:

    • Errors returned by the API are captured and presented with status codes and descriptive messages.
    • If "Continue On Fail" is disabled, the node execution stops on the first error.
    • To resolve errors, verify that the provided IDs are correct and that the API credentials have sufficient permissions.

Links and References

Discussion