Fatture in Cloud icon

Fatture in Cloud

Interact with Fatture in Cloud API

Actions67

Overview

This node integrates with the Fatture in Cloud API to manage various accounting and business resources. Specifically, for the Receipt resource with the Delete operation, it allows users to delete a receipt document from their Fatture in Cloud account.

Typical use cases include:

  • Automating cleanup of outdated or incorrect receipt records.
  • Integrating receipt management into broader workflows where receipts need to be programmatically removed based on certain conditions.
  • Synchronizing external systems by deleting receipts that no longer exist or are invalid.

Example: A user might set up an automation that deletes receipts older than a certain date or those flagged as duplicates, helping maintain accurate financial records.

Properties

Name Meaning
Company ID The numeric identifier of the company under which the receipt exists.
Document ID The numeric identifier of the specific receipt document to delete.

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 the API response data related to the deletion.
  • No binary data is produced by this operation.

Dependencies

  • Requires an active connection to the Fatture in Cloud API via an OAuth2-based API key credential.
  • The node depends on the internal Receipts module of the bundled code to perform the delete action.
  • Proper permissions on the Fatture in Cloud account are necessary to delete receipt documents.

Troubleshooting

  • Common issues:

    • Invalid or missing Company ID or Document ID parameters will cause the API call to fail.
    • Insufficient permissions or expired API credentials can lead to authorization errors.
    • Attempting to delete a non-existent receipt document will result in an error from the API.

  • Error messages:

    • "Fatture in Cloud API Error: <message>" indicates an issue returned by the API, such as validation errors or permission denials.
    • Status codes and detailed error information are included in the error description to help diagnose problems.

  • Resolutions:

    • Verify that the Company ID and Document ID are correct and correspond to existing entities.
    • Ensure the API credentials are valid and have the required scopes/permissions.
    • Use the node's "Continue On Fail" option to handle errors gracefully within workflows.

Links and References

Discussion