Fatture in Cloud icon

Fatture in Cloud

Interact with Fatture in Cloud API

Overview

This node integrates with the "Fatture in Cloud" API, a cloud invoicing and accounting platform. Specifically, for the Issued Document - Delete operation, it allows users to delete an issued document from their company account on Fatture in Cloud.

Typical use cases include:

  • Automating the removal of outdated or incorrect invoices or issued documents.
  • Cleaning up test data or erroneous entries in bulk workflows.
  • Integrating document lifecycle management into broader automation pipelines.

For example, a user might set up a workflow that deletes issued documents older than a certain date or removes documents flagged as duplicates.

Properties

Name Meaning
Company ID The numeric identifier of the company under which the issued document exists.
Document ID The numeric identifier of the specific issued document to be deleted.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will be confirmation data returned by the API indicating success or failure of the deletion.

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

No binary data is produced by this operation.

Dependencies

  • Requires an API authentication token credential configured in n8n to authenticate requests to the Fatture in Cloud API.
  • The node depends on the internal Issued Documents module of the bundled code to perform the delete operation.
  • Network access to the Fatture in Cloud API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Company ID or Document ID parameters will cause the API to reject the request.
    • Authentication failures due to expired or misconfigured API credentials.
    • Attempting to delete a non-existent document will result in an error response from the API.
    • Network connectivity problems can cause timeouts or unreachable errors.
  • Error messages:

    • Fatture in Cloud API Error: <message> indicates an error response from the API. The message often includes HTTP status and details.
    • Validation errors typically mention missing or invalid parameters.
  • Resolutions:

    • Verify that the Company ID and Document ID are correct and correspond to existing entities.
    • Ensure the API authentication token is valid and has sufficient permissions.
    • Check network connectivity and firewall settings.
    • Use the node's "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion