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
The node integrates with the Fatture in Cloud API, specifically supporting operations on various resources including E-Invoices. For the E-Invoice resource and the Verify XML operation, the node verifies the XML representation of an issued electronic invoice document.
This is useful in scenarios where you need to confirm that an e-invoice's XML data complies with required standards or has been correctly generated before sending it to tax authorities or clients. For example, a business automating its invoicing process can use this node to validate invoices programmatically, ensuring data integrity and compliance.
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 e-invoice document to verify the XML for. |
Output
- The output JSON contains the result of the XML verification for the specified e-invoice document.
- Typically, this will include validation status, any errors or warnings found in the XML, and possibly metadata about the document.
- The node does not explicitly output binary data for this operation; the focus is on JSON-formatted verification results.
Dependencies
- Requires an authenticated connection to the Fatture in Cloud API via an OAuth2 API credential.
- The node depends on the external Fatture in Cloud service being available and accessible.
- No additional environment variables are indicated beyond the OAuth2 credential setup.
Troubleshooting
Common issues:
- Invalid or missing Company ID or Document ID parameters will cause the API call to fail.
- Network connectivity problems or incorrect OAuth2 credentials will prevent successful API communication.
- If the XML document is malformed or does not meet the expected schema, the verification will return errors.
Error messages:
- Errors returned from the API are captured and presented with details including HTTP status and error messages.
- Example error:
Fatture in Cloud API Error: <error message>indicates an issue reported by the API. - To resolve, verify input parameters, check API credentials, and ensure the document exists and is properly formatted.
The node supports "continue on fail" mode, allowing workflows to proceed even if some items fail verification, returning error details in the output.