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 supplier data within a company. Specifically, the Supplier - Get operation retrieves detailed information about a particular supplier identified by its Supplier ID within a specified company.
Typical use cases include:
- Fetching supplier details for invoicing or payment processing.
- Synchronizing supplier data between Fatture in Cloud and other systems.
- Automating workflows that require supplier verification or reporting.
For example, a user might input a Company ID and Supplier ID to retrieve the supplier's contact information, tax details, or status to update their internal CRM or accounting software.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique numeric identifier of the company under which the supplier is registered. |
| Supplier ID | The unique numeric identifier of the supplier whose details are to be retrieved. |
Output
The node outputs JSON data representing the supplier's details as returned by the Fatture in Cloud API. This typically includes fields such as supplier name, contact information, tax codes, address, and other relevant metadata associated with the supplier.
If the node supports binary data output (not indicated here), it would represent attachments or documents related to the supplier, but this operation primarily returns structured JSON data.
Dependencies
- Requires an active connection to the Fatture in Cloud API via an OAuth2-based API key credential configured in n8n.
- The node depends on the
SuppliersModuleinternally to perform the API call. - Proper permissions and valid credentials are necessary to access supplier data.
Troubleshooting
Common Issues:
- Invalid or missing Company ID or Supplier ID will cause the API call to fail.
- Expired or misconfigured API credentials can lead to authentication errors.
- Network connectivity issues may prevent successful API communication.
Error Messages:
- Errors from the API are captured and presented with messages like "Fatture in Cloud API Error" followed by details.
- Validation errors from the API response may indicate incorrect IDs or insufficient permissions.
- To resolve, verify that the Company ID and Supplier ID are correct, ensure the API credentials are valid and have required scopes, and check network connectivity.
The node supports continuing on failure if enabled, allowing partial processing of multiple items.
Links and References
- Fatture in Cloud API Documentation (official API docs)
- n8n OAuth2 Credential Setup (for configuring API authentication)
This summary is based solely on static analysis of the provided source code and property definitions.