Fatture in Cloud

Overview

This node integrates with the Fatture in Cloud API to manage various accounting and business-related resources. Specifically, for the Received Document resource with the List operation, it retrieves a paginated list of received documents (such as expenses or passive notes) for a specified company. This is useful for automating bookkeeping tasks, auditing incoming invoices, or syncing received document data into other systems.

Practical examples include:

• Automatically fetching all expense documents received by a company for monthly accounting.
• Filtering received documents by type (e.g., only passive credit notes) to generate reports.
• Searching received documents using queries to find specific entries quickly.

Properties

Output

The node outputs an array of JSON objects representing the received documents matching the criteria. Each object contains fields depending on the selected fieldset and requested fields, such as document identifiers, dates, amounts, and types.

If binary data were involved (e.g., document attachments), it would be included in a separate binary property, but this operation focuses on JSON metadata about received documents.

Dependencies

• Requires an active 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 required beyond the configured API authentication.

Troubleshooting

• Common issues:

  • Invalid or missing Company ID will cause the API to reject the request.
  • Incorrect filter values (e.g., unsupported document type) may result in empty responses or errors.
  • Pagination parameters out of range might return no results.
  • Network or authentication failures can cause API errors.

• Error messages:

  • Unknown resource: receivedDocument — indicates a misconfiguration of the resource parameter.
  • Fatture in Cloud API Error: ... — generic API error with details; check the status code and message for specifics.
  • Validation errors from the API often include a validation_result explaining which input was invalid.

• Resolution tips:

  • Verify that the Company ID is correct and that the authenticated user has access.
  • Use valid filter options as documented.
  • Ensure the OAuth2 credentials are correctly set up and not expired.
  • Enable "Continue On Fail" if partial processing is acceptable when some items fail.

Links and References

• Fatture in Cloud API Documentation
• n8n OAuth2 Credential Setup
• Pagination Best Practices

If you need further details on other operations or resources, feel free to ask!