Actions20
Overview
This node integrates with the iCount accounting system to manage customers and documents. Specifically, for the Customer - List operation, it retrieves a list of customers from the iCount platform. This is useful when you want to fetch customer data in bulk for reporting, synchronization, or further processing within an automation workflow.
Practical examples:
- Automatically retrieving all customers to update a CRM system.
- Fetching a limited number of customers for batch invoicing.
- Combining all customer records into a single item for consolidated processing.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all customer results (true) or limit the number of returned customers (false). |
| Limit | When "Return All" is false, specifies the maximum number of customers to return (1-100). |
| Additional Fields | Extra options for listing customers: |
| Combine All Items | If true, returns all customers combined into a single item; if false, each customer is a separate item. |
Output
The output is an array of JSON objects representing customers retrieved from iCount. Each object corresponds to a customer record with its associated fields as provided by the iCount API.
If the "Combine All Items" option is enabled, the output will be a single JSON object containing all customers combined under one item.
No binary data output is involved in this operation.
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 to fetch customer data.
- Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
Common issues:
- Authentication failures due to invalid or expired API tokens.
- Exceeding API rate limits imposed by iCount.
- Network connectivity problems preventing access to the iCount API.
Error messages:
"Unknown operation: list"— indicates the operation parameter was not correctly set to "list".- API errors returned from iCount will be surfaced; ensure the API key has sufficient permissions.
Resolutions:
- Verify that the API key credential is valid and has required permissions.
- Check network connectivity and firewall settings.
- Use the "Return All" option carefully to avoid large data loads that might time out.
Links and References
- iCount API Documentation (official API docs, may require login)
- n8n documentation on creating custom nodes