Actions20
Overview
This node integrates with the iCount accounting system to create various types of financial documents. Specifically, the "Document - Create" operation allows users to generate new documents such as invoices, receipts, or other financial records within iCount. This is useful for automating document creation workflows in accounting, billing, and finance processes.
Typical scenarios include:
- Automatically generating invoices after a sales transaction.
- Creating payment receipts upon receiving payments.
- Issuing credit notes or other document types based on business needs.
For example, a user can configure this node to create an invoice document with specified client details, items sold, payment terms, and optionally send the invoice by email or download it as a PDF.
Properties
| Name | Meaning |
|---|---|
| Document Type | The type of document to create (e.g., invoice, receipt). Options are dynamically loaded from iCount. |
| Document Date | The date the document is issued. Defaults to the current date if not set. |
| Due Date | The payment due date for the document. |
| Currency | The currency code for the document. Options: שֶׁקֶל (ILS), דּוֹלָר (USD), יוֹרוֹ (EUR). Default is ILS. |
| Language | The language of the document. Options: Hebrew (he), English (en). Default is Hebrew. |
| Use Existing Client | Boolean flag indicating whether to use an existing client in iCount by ID or to provide new client details manually. |
| Client ID | The identifier of an existing client in iCount. Required if "Use Existing Client" is true. |
| Client Name | Full name of the client. Required if "Use Existing Client" is false. |
| HP Number | Client's identification number (e.g., company registration number or personal ID). Optional when creating a new client. |
| Client Email | Email address to send the document to. Optional when creating a new client. |
| Client Address | Client's physical address. Optional when creating a new client. |
| Client City | Client's city. Optional when creating a new client. |
| Client Phone | Client's phone number. Optional when creating a new client. |
| Items Input Type | How to input document items: either build manually via UI or provide a JSON array. Options: "Build Manually", "JSON Array". Default is "Build Manually". |
| Items JSON | JSON array of items/services included in the document. Required if "Items Input Type" is "JSON Array". Each item includes description, quantity, unit price, VAT type, discount, item code, and unit. |
| Items | Collection of items/services added manually. Required if "Items Input Type" is "Build Manually". Each item has fields for description, quantity, unit price, VAT type, discount percentage, item code, and unit of measure. |
| Add Payments | Boolean flag indicating whether to add payment information to the document. |
| Payments Input Type | How to input payments: either build manually or provide a JSON array. Options: "Build Manually", "JSON Array". Default is "Build Manually". |
| Payments JSON | JSON array of payments received. Required if "Payments Input Type" is "JSON Array". Payment types include cash, credit card, cheque, and bank transfer, each with relevant details like amount, bank info, card info, etc. |
| Payments | Collection of payments added manually. Required if "Payments Input Type" is "Build Manually". Includes payment type, amount, date, and additional fields depending on payment method (e.g., card details, bank account info). |
| Notes | Additional comments or notes to appear on the document. |
| Send by Email | Boolean flag to automatically send the created document to the client's email address. |
| Download PDF | Boolean flag to download the created document as a PDF file output (binary data). |
Output
The node outputs JSON data representing the created document's details as returned by the iCount API. This typically includes identifiers, status, totals, and metadata about the document.
If the "Download PDF" option is enabled, the node also outputs the document as a binary PDF file, allowing further processing or saving within n8n workflows.
Dependencies
- Requires an API key credential for authenticating with the iCount API.
- The node makes HTTP POST requests to iCount endpoints to perform operations.
- Proper configuration of the iCount API credentials in n8n is necessary.
- The node depends on dynamic loading of options such as document types and banks from the iCount API.
Troubleshooting
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- Invalid document type: If the selected document type is not recognized, verify that the document types are correctly loaded from iCount.
- Missing required fields: The node requires certain fields depending on whether an existing client is used or a new one is created; ensure all mandatory fields are provided.
- Malformed JSON input: When using JSON arrays for items or payments, ensure the JSON syntax is correct and matches expected structure.
- API rate limits or downtime: Network issues or API limits may cause failures; check connectivity and retry policies.
- Error messages from iCount API: These will be surfaced in the node output if "Continue On Fail" is enabled; review error messages for specific causes.
Links and References
- iCount API Documentation (official API docs, for reference)
- n8n documentation on Creating Custom Nodes
- General info on Accounting Document Types