iCount icon

iCount

ניהול מסמכים חשבונאיים ב-iCount

Overview

This node integrates with the iCount accounting system to manage customer data. Specifically, the "Customer Upsert" operation allows you to create a new customer or update an existing one in iCount based on the provided information. This is useful for synchronizing customer records from other systems or automating customer management workflows.

Common scenarios include:

  • Automatically adding new customers from an e-commerce platform into iCount.
  • Updating customer details such as contact info or payment terms when changes occur in your CRM.
  • Ensuring customer data consistency across multiple business applications.

For example, you could use this node to upsert a customer record with their name, contact details, and billing address whenever a new order is placed.

Properties

Name Meaning
Customer Name The full name of the customer (required).
HP Number Identification number (e.g., personal ID or company registration number).
Email Customer's email address.
First Name Customer's first name.
Last Name Customer's last name.
VAT ID VAT identification number (business tax ID).
Phone Customer's phone number.
Mobile Customer's mobile phone number.
Fax Customer's fax number.
Address Customer's street address.
City City of the customer's address.
Business Country Country of the customer's business address.
Business State State or region of the customer's business address.
Business City City of the customer's business address.
Business ZIP ZIP/postal code of the customer's business address.
Business Street Street name of the customer's business address.
Business Street Number Street number of the customer's business address.
Home Country Country of the customer's home address.
Home State State or region of the customer's home address.
Home City City of the customer's home address.
Home ZIP ZIP/postal code of the customer's home address.
Home Street Street name of the customer's home address.
Home Street Number Street number of the customer's home address.
Bank Customer's bank selected from a list of banks.
Branch Bank branch name or code.
Account Bank account number.
Foreign Account Foreign bank account number.
Notes Additional notes about the customer.
Digital Signature Customer's digital signature data.
Custom Client ID A custom identifier for the client.
Custom Info Custom additional information about the client.
Employee Assigned Employee assigned to the customer, selectable from a list of users.
Client Type Type/category of the client, selectable from predefined client types.
Client Type Name Name of the client type.
Payment Terms Payment terms expressed as number of days.
Client Type Discount Discount percentage associated with the client type.

Output

The node outputs JSON data representing the result of the upsert operation. This typically includes the customer record as stored or updated in iCount, containing all relevant fields such as IDs, names, addresses, and other metadata returned by the API.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the iCount API.
  • The node makes HTTP POST requests to the iCount API endpoints to perform operations.
  • Some properties load options dynamically by fetching lists of banks, users, and client types from the iCount API.
  • Proper configuration of the API authentication token in n8n credentials is necessary.

Troubleshooting

  • Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
  • Invalid input data: Required fields like "Customer Name" must be provided; missing required fields will cause errors.
  • Network issues: Connectivity problems to the iCount API endpoint can cause request failures.
  • Unexpected API responses: If the API returns unexpected data structures, the node may fail; verify that the iCount API version matches expectations.
  • Option loading failures: Dynamic dropdowns for banks, users, and client types depend on successful API calls; if these fail, check credentials and network access.

Links and References

Discussion