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 retrieve usage information about a company's subscription plan. Specifically, for the Company resource and the Get Plan Usage operation, it fetches usage statistics related to different categories such as clients, documents, products, or suppliers.
Typical use cases include:
- Monitoring how many clients or products a company has used relative to their subscription limits.
- Tracking document usage to avoid exceeding plan quotas.
- Automating reporting on supplier counts or other category usages within a company.
For example, a user might configure this node to get the current number of clients registered under a specific company ID to ensure they stay within their allowed plan limits.
Properties
| Name | Meaning |
|---|---|
| Company ID | The numeric identifier of the company for which to retrieve plan usage information. |
| Category | The category of usage data to retrieve. Options: Clients, Documents, Products, Suppliers. |
Output
The node outputs JSON data containing the usage details for the specified category within the given company. The exact structure depends on the API response but generally includes counts or metrics relevant to the chosen category (e.g., number of clients used).
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Fatture in Cloud API using OAuth2 authentication.
- The node expects valid credentials configured in n8n for accessing the Fatture in Cloud service.
- Network access to the Fatture in Cloud API endpoints is necessary.
Troubleshooting
Common issues:
- Invalid or missing company ID can cause errors or empty results.
- Incorrect category selection may lead to unexpected or no data.
- Authentication failures if the OAuth2 token is expired or misconfigured.
- API rate limits or network connectivity problems.
Error messages:
- Errors from the API are caught and reported with details including status code and message.
- If the node is set to continue on failure, error details are returned as part of the output JSON.
- Typical error descriptions include validation errors, unauthorized access, or unknown errors.
Resolutions:
- Verify that the company ID is correct and exists in the Fatture in Cloud system.
- Ensure the selected category matches one of the supported options.
- Check and refresh OAuth2 credentials if authentication errors occur.
- Review API usage limits and network settings.