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 interacts with the "Fatture in Cloud" API to list emails associated with a specified company. It is useful for automating retrieval of email records related to business operations, such as fetching sent or received emails for accounting, auditing, or communication tracking purposes.
Typical use cases include:
- Automatically retrieving and processing emails linked to a company’s financial documents.
- Integrating email data into workflows for reporting or notifications.
- Filtering and sorting emails based on specific criteria like date, fields, or query strings.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company whose emails you want to list. |
| Additional Fields | Optional parameters to customize the response: |
| - Fields | Comma-separated list of specific email fields to include in the response. |
| - Fieldset | Level of detail for the response; options are Basic or Detailed. |
| - Page | The page number of results to retrieve (pagination). |
| - Per Page | Number of email records per page (page size). |
| - Query | A search string to filter emails by content or metadata. |
| - Sort | Comma-separated list of fields to sort the results by (e.g., date, sender). |
Output
The node outputs an array of JSON objects representing emails retrieved from the Fatture in Cloud API. Each object contains email data according to the requested fields and fieldset level. The output includes metadata such as pagination details if applicable.
If binary data were involved (e.g., attachments), it would be included in a separate binary property, but this node focuses on JSON email data only.
Dependencies
- Requires an active connection to the Fatture in Cloud API via an OAuth2 API credential.
- The node depends on proper configuration of this API authentication within n8n.
- No additional external services are required beyond the Fatture in Cloud API.
Troubleshooting
Common Issues:
- Invalid or missing Company ID will cause the API call to fail.
- Incorrect pagination parameters may result in empty or incomplete results.
- Network or authentication errors can prevent successful API calls.
Error Messages:
- Errors returned from the API are captured and presented with status codes and messages.
- If the node is set to continue on failure, error details are output as JSON objects for each failed item.
- Typical error message format:
Fatture in Cloud API Error: <error message>, including HTTP status and response details.
Resolution Tips:
- Verify that the Company ID is correct and corresponds to an existing company in your Fatture in Cloud account.
- Check API credentials and ensure they have sufficient permissions.
- Adjust query, sorting, and pagination parameters to valid values.
- Enable "Continue On Fail" in the node settings to handle partial failures gracefully.
Links and References
- Fatture in Cloud API Documentation (official API docs)
- n8n OAuth2 Credential Setup (for configuring API authentication)