iCount icon

iCount

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

Actions20

Overview

This node integrates with the iCount accounting system to update customer information. It allows users to modify existing customer records by specifying the client ID and any fields that need updating. This is useful in scenarios where customer details change, such as address updates, contact information changes, or adjustments to payment terms.

Practical examples include:

  • Updating a customer's phone number or email after they provide new contact details.
  • Changing the assigned employee responsible for the customer.
  • Modifying billing or shipping addresses.
  • Adjusting client type or discounts based on updated agreements.

Properties

Name Meaning
Client ID The unique identifier of the customer to update (required).
Customer Name The full name of the customer.
HP Number The company's registration number.
Email Customer's email address.
First Name Customer's first name.
Last Name Customer's last name.
VAT ID VAT identification number or 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 business address.
Business State State or region of the business address.
Business City City of the business address.
Business ZIP ZIP or postal code of the business address.
Business Street Street name of the business address.
Business Street Number Street number of the business address.
Home Country Country of the home/residential address.
Home State State or region of the home/residential address.
Home City City of the home/residential address.
Home ZIP ZIP or postal code of the home/residential address.
Home Street Street name of the home/residential address.
Home Street Number Street number of the home/residential address.
Bank Bank associated with the customer. Options are dynamically loaded from the iCount API.
Branch Bank branch name or code.
Account Bank account number.
Foreign Account Foreign bank account number.
Notes Additional notes about the customer.
Digital Signature Digital signature string related to the customer.
Custom Client ID A custom identifier for the customer.
Custom Info Any custom information related to the customer.
Employee Assigned Employee assigned to this customer. Options are dynamically loaded from the iCount API.
Client Type Type/category of the client. Options are dynamically loaded from the iCount API.
Payment Terms Payment terms expressed as number of days.
Client Type Discount Discount percentage based on client type.

Output

The node outputs JSON data representing the updated customer record as returned by the iCount API. This typically includes all customer fields after the update operation, confirming the changes made.

If multiple items are processed, the output is an array of such JSON objects, each corresponding to one input item.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the iCount API.
  • Uses HTTP POST requests to the iCount API endpoints.
  • Dynamic options for some properties (Bank, Employee Assigned, Client Type) are fetched via API calls during node configuration.
  • The node expects proper network connectivity to the iCount service.

Troubleshooting

  • Common issues:

    • Invalid or missing Client ID will cause the update to fail.
    • Incorrect API credentials or expired tokens will result in authentication errors.
    • Network issues may prevent communication with the iCount API.
    • Providing invalid field values (e.g., wrong data types or unsupported codes) can cause API errors.

  • Error messages:

    • "Unknown operation: update" — indicates the operation parameter was not recognized; ensure "Update" is selected.
    • Authentication errors usually mention authorization failure; verify API key validity.
    • Validation errors from the API will be included in the error message; check that all required fields are correctly formatted.

  • Resolution tips:

    • Double-check the Client ID exists in iCount before attempting update.
    • Ensure API credentials are correctly configured in n8n.
    • Validate input data types and formats according to iCount requirements.
    • Use the "Continue On Fail" option to handle partial failures gracefully.

Links and References

Discussion