Fatture in Cloud icon

Fatture in Cloud

Interact with Fatture in Cloud API

Overview

This node integrates with the Fatture in Cloud API to list tax records of type "F24" for a specified company. It is useful for retrieving and managing tax-related data such as payments or filings associated with a company’s fiscal activities.

Typical use cases include:

  • Fetching paginated lists of tax records for reporting or auditing.
  • Filtering tax records by search queries or sorting them by specific fields.
  • Selecting detailed or basic information about each tax record depending on the needs of the workflow.

For example, an accountant could automate the retrieval of all tax filings for a company within a certain period, filter them by status, and then process or export this data further downstream.

Properties

Name Meaning
Company ID The numeric identifier of the company whose tax records you want to list.
Filter Options A collection of optional filters to refine the list results:
- Fields Comma-separated list of specific fields to include in the response (e.g., "id,date,amount").
- Fieldset Choose between "Basic" or "Detailed" sets of fields returned for each tax record.
- Page The page number for pagination (default is 1).
- Per Page Number of results per page (default is 50).
- Query Search query string to filter the tax records based on matching criteria.
- Sort Sorting order for the results, e.g., by date ascending or descending.

Output

The node outputs an array of JSON objects representing tax records (F24) retrieved from the API. Each object contains fields according to the selected fieldset ("basic" or "detailed") and any additional requested fields.

If binary data were involved (not indicated here), it would be summarized accordingly, but this operation returns only JSON data.

Dependencies

  • Requires an active connection to the Fatture in Cloud API via OAuth2 authentication.
  • The node expects valid credentials configured in n8n to authenticate API requests.
  • No other external dependencies are required.

Troubleshooting

  • Common issues:

    • Invalid or missing Company ID will cause the API to reject the request.
    • Incorrect filter parameters (e.g., invalid field names in "Fields") may result in empty responses or errors.
    • Pagination parameters out of range might return no results.
  • Error messages:

    • Errors from the API are caught and reported with details including HTTP status and error message.
    • If the node is set to continue on fail, errors for individual items will be output as JSON objects containing error details.
    • Typical error resolution involves verifying the company ID, ensuring correct filter syntax, and checking API credential validity.

Links and References


This summary is based solely on static analysis of the provided source code and property definitions.

Discussion