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 integrates with the Fatture in Cloud API, specifically allowing users to interact with various resources such as receipts, companies, clients, issued documents, and more. For the Receipt - Get operation, it retrieves detailed information about a specific receipt document associated with a company.
Typical use cases include:
- Fetching receipt details for accounting or auditing purposes.
- Automating retrieval of receipt data to integrate with other financial or ERP systems.
- Verifying receipt information before processing payments or refunds.
Example: A user wants to get the details of a receipt with ID 12345 for company ID 67890 to verify the transaction before issuing a refund.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique numeric identifier of the company that owns the receipt. |
| Document ID | The unique numeric identifier of the receipt document to retrieve. |
Output
The node outputs JSON data representing the receipt's details as returned by the Fatture in Cloud API. This typically includes fields such as receipt number, date, amount, supplier info, tax details, and any other metadata related to the receipt.
If multiple input items are processed, the output is an array where each element corresponds to the receipt data for the respective input item.
The node does not output binary data for this operation.
Dependencies
- Requires an active connection to the Fatture in Cloud API using OAuth2 authentication.
- The node expects valid credentials configured in n8n for accessing the Fatture in Cloud service.
- Network access to the Fatture in Cloud API endpoints is necessary.
Troubleshooting
Common issues:
- Invalid or expired API credentials will cause authentication failures.
- Providing incorrect company or document IDs may result in "not found" errors.
- Network connectivity problems can lead to timeouts or unreachable API errors.
Error messages:
Fatture in Cloud API Error: <message>indicates an error response from the API. The message often contains details like validation errors or missing parameters.- If the node throws an error mentioning "Unknown resource," it means the specified resource name is invalid or unsupported.
- Validation errors usually indicate missing required properties like Company ID or Document ID.
Resolutions:
- Verify that the API credentials are correctly set up and have sufficient permissions.
- Double-check the Company ID and Document ID values for correctness.
- Ensure stable internet connectivity and that the Fatture in Cloud API is reachable.
- Use the "Continue on Fail" option if you want the workflow to proceed despite individual item errors.