Actions20
Overview
This node integrates with the iCount accounting system to update an existing contact associated with a customer. It allows users to modify various details of a customer’s contact, such as name, contact type, email, phone numbers, address information, and notes.
Typical use cases include:
- Keeping customer contact information up-to-date in iCount after changes in your CRM or other systems.
- Automating updates to multiple contacts’ details in bulk workflows.
- Synchronizing contact data between iCount and external databases or applications.
For example, you might use this node to update a contact’s email and phone number when they change jobs or roles within a client company.
Properties
| Name | Meaning |
|---|---|
| Client ID | The unique identifier of the customer to whom the contact belongs. |
| Contact ID | The unique identifier of the contact to update. |
| Contact Name | The full name of the contact person. |
| Contact Type | The category/type of the contact (loaded dynamically from iCount). |
| The contact’s email address. | |
| Phone | The contact’s phone number. |
| Mobile | The contact’s mobile phone number. |
| Fax | The contact’s fax number. |
| First Name | The contact’s first name. |
| Last Name | The contact’s last name. |
| Company Name | The company name associated with the contact. |
| ID Number | Identification number (e.g., personal ID or business registration number). |
| Business Country | Country for the business address. |
| Business City | City for the business address. |
| Business ZIP | ZIP/postal code for the business address. |
| Business Street | Street name for the business address. |
| Business Street Number | House/building number for the business address. |
| Home Country | Country for the home/residential address. |
| Home City | City for the home/residential address. |
| Home ZIP | ZIP/postal code for the home/residential address. |
| Home Street | Street name for the home/residential address. |
| Home Street Number | House/building number for the home/residential address. |
| Date of Birth | Contact’s date of birth in YYYY-MM-DD format. |
| Notes | Additional notes or comments about the contact. |
Output
The node outputs JSON data representing the updated contact record as returned by the iCount API. This typically includes all the fields of the contact after the update operation, confirming the new state of the contact in the system.
No binary data output is involved.
Dependencies
- Requires an active connection to the iCount API via an API key credential configured in n8n.
- The node uses HTTP POST requests to communicate with iCount endpoints.
- The "Contact Type" options are dynamically loaded from iCount using the API.
Troubleshooting
Common issues:
- Invalid or missing Client ID or Contact ID will cause the update to fail.
- Incorrect API credentials or expired tokens will result in authentication errors.
- Providing invalid date formats (for Date of Birth) may cause validation errors.
- Network connectivity problems can prevent communication with the iCount API.
Error messages:
"Unknown operation: updateContact": Indicates the operation parameter was not set correctly.- API error responses usually contain descriptive messages; ensure required fields are provided.
- If the node returns an error about missing permissions, verify that the API key has rights to update contacts.
Resolution tips:
- Double-check IDs and required fields before running the node.
- Ensure the API key credential is valid and has necessary scopes.
- Validate date formats and string lengths according to iCount API documentation.
- Use the "Continue on Fail" option in n8n to handle partial failures gracefully.
Links and References
- iCount API Documentation (general reference for API endpoints and data formats)
- n8n Documentation on Creating Custom Nodes (for extending or debugging nodes)