Actions20
Overview
The node integrates with the iCount accounting system to perform various document-related operations. Specifically, the Search operation under the Document resource allows users to search for documents such as invoices, receipts, orders, and offers based on multiple filter criteria. This is useful for retrieving specific financial or transactional documents from iCount for reporting, auditing, or further processing.
Typical use cases include:
- Finding all invoices issued to a particular client within a date range.
- Retrieving documents of a certain type (e.g., receipts) that are still open.
- Extracting detailed document data for integration with other systems or dashboards.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching results or limit the number of results returned. |
| Max Results | Maximum number of results to return when "Return All" is false. Range: 0-1000. |
| Detail Level | Level of detail in the returned document information. Options: Basic (doctype+docnum), Standard (+ date, client, total), Detailed (+ client details, totals), Extended (+ employee, income type), Full (+ foreign currency), Complete (Everything). |
| Filters | Collection of filters to narrow down the search results: |
| - Client ID | Numeric identifier of the client. |
| - Client Name | Name of the client. |
| - Client Email | Email address of the client. |
| - VAT ID | VAT identification number (ח.פ / ע.מ). |
| - Document Type | Type of document. Options: Invoice, Invoice Receipt, Receipt, Refund, Order, Offer, Delivery, Deal. |
| - Document Number | Specific document number. |
| - Document Status | Status of the document. Options: Open, Closed, Partially Closed. |
| - Start Date | Start date for filtering documents by issue date. |
| - End Date | End date for filtering documents by issue date. |
| - Due Date (Start) | Start date for filtering documents by due date. |
| - Due Date (End) | End date for filtering documents by due date. |
| - Sort Field | Field to sort the results by. Options: Issue Date, Issue Time, Document Number, Payment Date, Client Name. |
| - Sort Order | Sort direction. Options: Ascending (ASC), Descending (DESC). |
| - Offset | Number of results to skip (for pagination). |
| - Get Base Documents | Whether to also return base documents related to the found documents. |
Output
The output is an array of JSON objects representing the documents matching the search criteria. Each object contains fields according to the selected detail level, ranging from basic identifiers (document type and number) to comprehensive details including client info, totals, employee data, income types, and foreign currency information.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the iCount API.
- The node makes HTTP POST requests to the iCount API endpoints.
- Proper configuration of the API key credential in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing invalid filter values (e.g., incorrect date formats or unsupported document types) may result in errors or empty results.
- Requesting too many results without enabling "Return All" might truncate data unexpectedly.
Error messages:
"Unknown operation: search"— indicates the operation parameter was not set correctly; ensure "Search" is selected under the Document resource.- API errors returned from iCount (e.g., rate limits, invalid parameters) will be propagated; check the error message for details.
Resolutions:
- Verify API credentials and permissions.
- Validate input parameters before execution.
- Use pagination (Offset + Max Results) or enable "Return All" carefully to manage large datasets.
Links and References
- iCount API Documentation (official API docs, if publicly available)
- n8n documentation on creating custom nodes