Actions20
Overview
This node integrates with the iCount accounting system to retrieve open documents related to customers. Specifically, the "Get Open Docs" operation fetches all open (unsettled or pending) documents for customers. It can return documents for a specific customer if a Client ID is provided, or for all customers if left empty.
Typical use cases include:
- Monitoring outstanding invoices or receipts for customers.
- Automating follow-ups on unpaid or open financial documents.
- Integrating open document data into other workflows such as CRM or notification systems.
For example, a business could use this node to pull all open invoices for a particular client and send automated reminders.
Properties
| Name | Meaning |
|---|---|
| Client ID (Optional) | Specific customer identifier to filter open documents. If empty, retrieves for all clients. |
| Additional Options | A collection of optional filters and flags: |
| - Document Type | Filter by type of document. Options: Invoice Receipt, Tax Invoice, Receipt, Refund, Deal. |
| - Get Items | Boolean flag indicating whether to also return line items/details of each document. |
| - Client Email | Filter documents by customer's email address. |
| - Client Name | Filter documents by customer's name. |
Output
The node outputs an array of JSON objects representing the open documents matching the criteria. Each object corresponds to one open document and includes its details such as document type, status, customer info, and optionally the line items if requested.
If the "Get Items" option is enabled, each document's output will also contain detailed items associated with that document.
No binary data output is produced by 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 authentication token in n8n credentials is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrect Client ID or filters may result in empty responses.
- Network connectivity problems can prevent API calls from succeeding.
Error messages:
"Unknown operation: getOpenDocs"indicates a misconfiguration of the operation parameter.- API errors from iCount (e.g., unauthorized, bad request) will be propagated; ensure credentials and parameters are correct.
Resolutions:
- Verify the API key credential is correctly set up and has sufficient permissions.
- Double-check input parameters like Client ID, email, and document type filters.
- Enable "Continue On Fail" in the node settings to handle partial failures gracefully.
Links and References
- iCount API Documentation (official API docs, for reference)
- n8n documentation on creating custom nodes