Actions13
- Customers Actions
- Documents Actions
- PDF-Templates Actions
- Attachments Actions
- Document-Payments Actions
Overview
This node integrates with the Easybill API to retrieve payment information related to documents. Specifically, the "Get Document-Payments" operation fetches a list of payments made on one or more documents, allowing filtering by document IDs, payment dates, and references. This is useful for accounting automation, financial reconciliation, or reporting scenarios where you need to programmatically access payment data associated with invoices or other billing documents.
Practical examples include:
- Automatically retrieving recent payments to update your internal accounting system.
- Filtering payments within a specific date range for monthly financial reports.
- Fetching payments linked to particular documents to verify payment status.
Properties
| Name | Meaning |
|---|---|
| Limit | Limits the number of results returned. Default is 100, maximum is 1000. |
| Page | Specifies the page number of results to fetch. Default is 1. |
| Document ID(s) | Filter payments by one or multiple document IDs (comma-separated). |
| Payment Date | Filter payments by payment date; supports a single date or a date range (comma-separated). |
| Reference(s) | Filter payments by one or multiple payment references (comma-separated). |
Output
The node outputs an array of JSON objects representing document payment records retrieved from Easybill. Each object contains details about individual payments such as payment amount, date, reference, and associated document ID. The exact structure depends on the Easybill API response but typically includes fields relevant to payment transactions.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Easybill API via an API key credential configured in n8n.
- The node relies on Easybill's REST API endpoints to fetch document payment data.
- No additional external dependencies beyond the Easybill API and its authentication are needed.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing invalid filter values (e.g., malformed dates or non-existent document IDs) may result in empty responses or errors.
- Exceeding the maximum limit (over 1000) will likely be rejected by the API.
Error messages:
- Authentication errors indicate problems with the API key setup; verify credentials in n8n.
- Validation errors suggest incorrect input parameters; check the format of filters like dates and IDs.
- Network or timeout errors may occur if the Easybill API is unreachable; ensure network connectivity.
Links and References
- Easybill API Documentation (for detailed API endpoint info)
- n8n documentation on creating and using API credentials