Fatture in Cloud icon

Fatture in Cloud

Interact with Fatture in Cloud API

Actions67

Overview

The node integrates with the Fatture in Cloud API to manage clients within a company. Specifically, the Client - Create operation allows users to add new client records to their Fatture in Cloud account. This is useful for automating client management workflows such as onboarding new customers, syncing CRM data, or preparing client information for invoicing and accounting.

Practical examples include:

  • Automatically creating a client record when a new lead is qualified in a CRM.
  • Syncing client details from an external database into Fatture in Cloud.
  • Adding detailed client contact and address information programmatically to streamline billing processes.

Properties

Name Meaning
Company ID The numeric identifier of the company under which the client will be created. This is required to specify the context for the client creation.
Client Name The name of the client to create. This is a mandatory string field representing the client's official or business name.
Additional Fields A collection of optional fields to provide more detailed client information. These include:
- Address City, Extra, Postal Code, Province, Street
- Certified Email (PEC)
- Client Code
- Contact Person
- Country (default "Italia")
- E-Invoice (boolean)
- Electronic Invoice Code
- Email
- Fax
- First Name
- Last Name
- Notes
- Phone
- Tax Code
- Type (Company or Person)
- VAT Number

Output

The node outputs JSON data representing the newly created client object as returned by the Fatture in Cloud API. Each output item corresponds to one input item processed and contains the full client data including all submitted fields and any additional metadata provided by the API.

The node does not output binary data.

Dependencies

  • Requires an OAuth2 API credential configured for Fatture in Cloud to authenticate requests.
  • Depends on the Fatture in Cloud API being accessible and the user having appropriate permissions to create clients within the specified company.
  • No other external dependencies are needed beyond the n8n environment and the configured credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing Company ID: The API requires a valid company context; ensure the company ID exists and is correct.
    • Missing required fields like Client Name will cause validation errors.
    • Authentication failures if the OAuth2 token is expired or misconfigured.
    • Network or API downtime can cause request failures.

  • Error messages:

    • Errors from the API are caught and reported with details including status code and error message.
    • Validation errors typically indicate which fields are missing or invalid.
    • If continueOnFail is enabled, errors for individual items are returned as error objects instead of stopping execution.

  • Resolution tips:

    • Verify all required parameters are set correctly.
    • Check and refresh OAuth2 credentials if authentication fails.
    • Review API error messages for specific field issues.
    • Use continueOnFail cautiously to handle partial failures gracefully.

Links and References

Discussion