Actions67
- Archive Document Actions
- Cashbook Actions
- Client Actions
- Company Actions
- E-Invoice Actions
- Email Actions
- Info Actions
- Issued Document Actions
- Product Actions
- Receipt Actions
- Received Document Actions
- Setting Actions
- Supplier Actions
- Tax (F24) Actions
- Webhook Actions
Overview
This node interacts with the "Fatture in Cloud" API, a cloud invoicing and accounting platform. Specifically, for the Received Document resource with the Delete operation, it deletes a received document identified by its document ID within a specified company.
Common scenarios where this node is beneficial include automating bookkeeping workflows, such as removing outdated or incorrect received invoices or bills from the system programmatically. For example, an accountant might use this node to clean up test documents after data import or to automate document lifecycle management in integration with other systems.
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 to delete. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will be a confirmation of deletion or an empty object if successful. If the operation fails, the output will contain error details describing what went wrong.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Fatture in Cloud API using an OAuth2-based API key credential.
- The node depends on proper configuration of this API authentication within n8n.
- Network access to the Fatture in Cloud service endpoint is necessary.
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 document will return an error from the API.
Error Messages:
- Errors returned from the API are captured and presented with status codes and messages.
- Typical error message format:
Fatture in Cloud API Error: <error message>, including HTTP status and detailed response data.
Resolution Tips:
- Verify that the Company ID and Document ID are correct and correspond to existing entities.
- Ensure the API credentials are valid and have sufficient permissions.
- Use the "Continue On Fail" option in the node settings to handle errors gracefully during batch operations.
Links and References
- Fatture in Cloud Official Website
- Fatture in Cloud API Documentation (for detailed API endpoints and error codes)