Actions34
- Banking Operation (India) Actions
- Catalog Operation Actions
- Contact Operation Actions
- HRMS Operation (India) Actions
- Purchase Operation (India) Actions
- Sales Operation (India) Actions
- Tax Operation (India) Actions
Overview
This node interacts with the Sales Operation (India) resource of the LEDGERS API, specifically supporting the "List Invoices" operation. It allows users to retrieve a list of invoices filtered by various criteria such as payment status, date range, and contact ID. This is useful for businesses that want to automate invoice management, reporting, or integration with other systems.
Practical examples include:
- Fetching all paid invoices within a specific date range for reconciliation.
- Listing unpaid or partially paid invoices to follow up on outstanding payments.
- Filtering invoices related to a particular customer/contact for detailed analysis.
Properties
| Name | Meaning |
|---|---|
| Limit | The maximum number of invoices to return in one request. |
| Filters | A collection of optional filters to narrow down the invoice list: |
| - Payment Status | Filter invoices by their payment status. Options: Paid, Not Paid, Part Paid, Deleted. |
| - Date From | Start date to filter invoices from (inclusive). |
| - Date To | End date to filter invoices up to (inclusive). |
| - Contact ID | Filter invoices associated with a specific contact/customer ID. |
Output
The node outputs JSON data containing the list of invoices matching the specified filters and limit. Each item in the output corresponds to an invoice record with its details as returned by the LEDGERS API.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the LEDGERS API.
- Requires valid user credentials (email and password) for login to obtain an API token.
- The node makes HTTP requests to the LEDGERS API endpoints to fetch invoice data.
- Proper configuration of the API URL and credentials in n8n is necessary.
Troubleshooting
- Authentication failures: If the node returns errors about authentication, verify that the API key, email, and password credentials are correct and have sufficient permissions.
- Empty or no data returned: Check if the filters are too restrictive or if there are no invoices matching the criteria.
- API rate limits or connectivity issues: Network problems or API throttling may cause request failures; retry or check API usage limits.
- Invalid date formats: Ensure date inputs are correctly formatted as dates without time components.
Links and References
- LEDGERS API Documentation (generic link, replace with actual if available)
- n8n documentation on HTTP Request Node for understanding API calls
- General guidance on Invoice Management Best Practices