Actions20
Overview
This node integrates with the iCount accounting system to manage customer-related data. Specifically, the "Get Contacts" operation under the "Customer" resource retrieves all contact persons associated with a specified customer. This is useful in scenarios where you need to access or process detailed contact information for clients stored in iCount, such as for CRM purposes, sending notifications, or syncing contacts with other systems.
Practical example:
You have a workflow that triggers when a new invoice is created for a customer. You want to fetch all contact persons related to that customer to send them an email notification. Using this node's "Get Contacts" operation, you can retrieve those contacts and then loop through them to send personalized messages.
Properties
| Name | Meaning |
|---|---|
| Client ID | The unique numeric identifier of the customer whose contacts you want to retrieve. |
Output
The node outputs an array of JSON objects representing the contacts linked to the specified customer. Each object contains the details of a single contact person, such as name, phone number, email, and any other contact-specific fields provided by the iCount API.
If multiple contacts exist, the output will be an array with one entry per contact.
The node does not output binary data.
Dependencies
- Requires an active connection to the iCount API via an API key credential.
- The node makes HTTP POST requests to the iCount API endpoints.
- Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
Common issues:
- Invalid or missing API authentication token will cause authorization errors.
- Providing a non-existent or incorrect Client ID may result in empty results or errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
"Unknown operation: getContacts": Indicates the operation parameter was set incorrectly; ensure "Get Contacts" is selected.- API errors returned from iCount (e.g., 401 Unauthorized) usually mean the API key is invalid or expired.
- If the node returns an error about missing required parameters, verify that the Client ID is provided and is a valid number.
Resolution tips:
- Double-check the API key credential setup.
- Confirm the Client ID exists in your iCount account.
- Enable "Continue On Fail" in the node settings to handle errors gracefully during batch processing.
Links and References
- iCount API Documentation (official API docs, for reference on endpoints and data structures)
- n8n documentation on creating custom nodes (for understanding node development concepts)