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 focusing on the "E-Invoice" resource and its operations. The Get Rejection Reason operation retrieves the reason why a particular electronic invoice document was rejected by the system or tax authority.
This node is beneficial in scenarios where users need to automate monitoring and handling of electronic invoices, especially to quickly identify and respond to rejected invoices. For example, an accounting team can use this node to fetch rejection reasons automatically and trigger notifications or corrective workflows.
Properties
| Name | Meaning |
|---|---|
| Company ID | The numeric identifier of the company for which the e-invoice operation is performed. |
| Document ID | The numeric identifier of the issued electronic invoice document whose rejection reason is requested. |
Output
The output is a JSON array containing the details returned by the Fatture in Cloud API for the rejection reason of the specified e-invoice document. The structure typically includes fields describing the rejection cause, such as error codes, messages, or validation results provided by the API.
No binary data output is expected from this operation.
Dependencies
- Requires an active connection to the Fatture in Cloud API.
- Requires an API authentication token configured via OAuth2 credentials within n8n.
- The node depends on the internal
EInvoicesModuleclass that handles communication with the e-invoices endpoints of the API.
Troubleshooting
Common Issues:
- Invalid or missing Company ID or Document ID parameters will cause the API call to fail.
- Authentication errors if the OAuth2 token is expired or misconfigured.
- Network connectivity issues preventing access to the Fatture in Cloud API.
Error Messages:
- Errors returned from the API are captured and presented with details including status code and message.
- If the node is set to continue on failure, errors are returned as part of the output JSON with an
errorfield. - Typical error messages include validation failures or unauthorized access, which require checking input parameters and credential validity.
Links and References
- Fatture in Cloud API Documentation (official API docs for further details on e-invoice operations)
- n8n OAuth2 Credential Setup Guide (for configuring API authentication)
This summary is based solely on static analysis of the provided source code and property definitions.