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 to manage clients within a specified company. The "Get Many" operation under the "Client" resource retrieves multiple client records associated with a given company ID. It supports fetching either all clients or a limited number based on user preference.
Typical use cases include:
- Synchronizing client lists from Fatture in Cloud into other systems.
- Generating reports or analytics on client data.
- Automating workflows that require bulk access to client information.
For example, a user might want to fetch all clients of a particular company to update their CRM system or send batch communications.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company whose clients are to be retrieved. |
| Return All | Whether to return all client records (true) or limit the number of results (false). |
| Limit | When Return All is false, this sets the maximum number of client records to retrieve. |
Output
The node outputs an array of JSON objects representing client data retrieved from the Fatture in Cloud API. Each object corresponds to a single client and contains fields as defined by the API's client schema (e.g., client name, contact details, identifiers).
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Fatture in Cloud API using an OAuth2-based API key credential.
- The node depends on the Fatture in Cloud API being accessible and the provided company ID being valid.
- No additional external services or environment variables are required beyond the configured API authentication.
Troubleshooting
Common Issues:
- Invalid or missing company ID will cause the API call to fail.
- Network connectivity problems can prevent successful API communication.
- Insufficient permissions or expired credentials may result in authorization errors.
Error Messages:
- Errors returned by the API are captured and presented with details including status code and message.
- If the node is set to continue on failure, error details for individual items are included in the output.
- Typical error messages include validation errors, unauthorized access, or resource not found.
Resolution Tips:
- Verify the company ID is correct and exists in the Fatture in Cloud account.
- Ensure the API credentials are valid and have necessary permissions.
- Check network connectivity and retry if transient issues occur.
- Enable "Continue On Fail" to handle partial failures gracefully during batch operations.