Actions20
Overview
This node integrates with the iCount system to manage customer data, specifically allowing you to add a new contact person to an existing customer record. It is useful in scenarios where you need to maintain detailed contact information for clients, such as sales teams managing multiple contacts per client or support departments tracking various points of communication.
For example, if your CRM stores customers but you want to enrich each customer with multiple contacts (e.g., billing contact, technical contact), this node lets you add those contacts programmatically during workflow automation.
Properties
| Name | Meaning |
|---|---|
| Client ID | The unique identifier of the customer to whom the contact will be added. |
| First Name | Contact's first name. |
| Last Name | Contact's last name. |
| Company Name | The company name associated with the contact. |
| ID Number | Identification number (e.g., personal ID, VAT number). |
| Contact Type | The type/category of the contact person. Options are dynamically loaded from iCount. |
| Contact's email address. | |
| Phone | Contact's phone number. |
| Mobile | Contact's mobile phone number. |
| Fax | Contact's fax number. |
| Position | Job title or position of the contact within the company. |
| Business Country | Country of the business address. |
| Business City | City of the business address. |
| Business ZIP | ZIP/postal code of the business address. |
| Business Street | Street name of the business address. |
| Business Street Number | Building number of the business address. |
| Home Country | Country of the home address. |
| Home City | City of the home address. |
| Home ZIP | ZIP/postal code of the home address. |
| Home Street | Street name of the home address. |
| Home Street Number | Building number of the home 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 newly added contact details as returned by the iCount API. This typically includes confirmation of the contact creation and the contact's stored information.
No binary data output is involved.
Dependencies
- Requires an active connection to the iCount API via an API key credential.
- The node uses HTTP POST requests to interact with iCount endpoints.
- Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
Common issues:
- Invalid or missing Client ID: The contact cannot be added without specifying a valid existing customer.
- Incorrect API credentials or expired token: Authentication failures will prevent contact creation.
- Missing required fields or invalid data formats (e.g., date of birth not in YYYY-MM-DD) may cause errors.
Error messages:
"Unknown operation: addContact": Indicates a misconfiguration in the operation parameter; ensure "Add Contact" is selected.- API response errors related to authorization or validation will be passed through; check API key validity and input data correctness.
Resolution tips:
- Verify that the Client ID corresponds to an existing customer in iCount.
- Ensure all required fields are provided and formatted correctly.
- Confirm that the API key credential is set up and has sufficient permissions.
Links and References
- iCount API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating custom nodes for further customization guidance