Actions20
Overview
This node integrates with the iCount accounting system, enabling automation of various customer and document management tasks. Specifically, for the Customer - Get operation, it retrieves detailed information about a specific customer using their unique client ID within iCount.
Typical use cases include:
- Fetching customer details to enrich CRM data.
- Validating customer existence before processing orders or invoices.
- Automating reporting workflows that require up-to-date customer information.
For example, you might use this node to get a customer's billing address and contact info before generating an invoice in your workflow.
Properties
| Name | Meaning |
|---|---|
| Client ID | The unique identifier of the customer in iCount whose details you want to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the customer details fetched from iCount. The structure typically includes fields such as customer name, contact information, addresses, and other metadata associated with the customer record.
If multiple customers are returned (not typical for a single "Get" by ID), the output will be an array of customer objects.
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 iCount's REST API endpoints.
- Proper configuration of the iCount API credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Client ID: The node requires a valid client ID; ensure this is correctly provided.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network or API downtime: Check connectivity and iCount service status if requests fail.
Error messages:
"Unknown operation: get": Indicates a misconfiguration of the operation parameter; ensure "Get" is selected under Customer resource.- API response errors usually include descriptive messages; review these to adjust inputs or credentials.
Links and References
- iCount API Documentation (official API docs for further details on customer endpoints)
- n8n documentation on creating custom nodes