Fatture in Cloud icon

Fatture in Cloud

Interact with Fatture in Cloud API

Overview

This node integrates with the "Fatture in Cloud" API to manage suppliers within a company’s accounting system. Specifically, the Supplier - Create operation allows users to add new supplier records to their company database.

Typical use cases include automating supplier onboarding processes, syncing supplier data from other systems, or bulk-creating suppliers based on external data sources. For example, an accounting team can automatically create supplier entries when new vendors are approved, ensuring consistent and up-to-date supplier information without manual entry.

Properties

Name Meaning
Company ID The numeric identifier of the company under which the supplier will be created.
Supplier Name The name of the supplier to be created.
Additional Fields Optional extra details about the supplier. These include:
- Address City: Supplier city
- Address Extra: Additional address info
- Address Postal Code: Supplier postal code
- Address Province: Supplier province
- Address Street: Supplier street address
- Certified Email: Supplier certified email (PEC)
- Code: Supplier code
- Contact Person: Name of contact person
- Country: Supplier country (default is "Italia")
- Email: Supplier email
- Fax: Supplier fax number
- First Name: Supplier first name (for person type)
- Last Name: Supplier last name (for person type)
- Notes: Additional notes about the supplier
- Phone: Supplier phone number
- Tax Code: Supplier tax code
- Type: Supplier type, either "Company" or "Person"
- VAT Number: Supplier VAT number

Output

The node outputs JSON data representing the newly created supplier record as returned by the Fatture in Cloud API. This typically includes the supplier's unique ID, all submitted fields, and any additional metadata provided by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Fatture in Cloud API via OAuth2 authentication.
  • The node expects valid credentials configured in n8n for accessing the Fatture in Cloud service.
  • The companyId must correspond to a valid company accessible by the authenticated user.

Troubleshooting

  • Common Issues:

    • Invalid or missing companyId: The API will reject requests if the company ID does not exist or the user lacks access.
    • Missing required fields such as supplierName will cause validation errors.
    • Network or authentication failures may prevent successful API calls.
  • Error Messages:

    • Errors returned from the API are captured and presented with status codes and messages.
    • Validation errors from the API include detailed descriptions of missing or invalid fields.
    • If the node is set to continue on failure, error details are included in the output JSON for each failed item.
  • Resolution Tips:

    • Verify that the OAuth2 credentials are correctly configured and have sufficient permissions.
    • Ensure the companyId is correct and the user has access rights.
    • Provide all required fields and validate optional fields according to API documentation.
    • Check network connectivity and API service status if errors persist.

Links and References

Discussion