Actions13
- Customers Actions
- Documents Actions
- PDF-Templates Actions
- Attachments Actions
- Document-Payments Actions
Overview
This node integrates with the Easybill API to create a payment record associated with a specific document (such as an invoice). It allows users to register payments made towards documents, including partial payments, overdue fees, and various payment details like type, provider, and reference.
Common scenarios where this node is beneficial include:
- Automating the recording of customer payments in Easybill after receiving payment confirmation.
- Keeping financial records up-to-date by linking payments directly to invoices or other documents.
- Handling partial payments and marking documents as paid even if the full amount isn't covered.
- Tracking different payment methods and providers for reporting or reconciliation purposes.
Practical example:
- After a customer pays an invoice via Stripe, this node can be used to create a payment entry in Easybill specifying the amount, payment date, payment type ("Stripe"), and mark the invoice as partially or fully paid.
Properties
| Name | Meaning |
|---|---|
| Document | Select the target document (e.g., invoice) to which the payment applies. Can be selected from a list or specified by ID. |
| Amount (in cents) | The payment amount expressed in cents (e.g., 1000 = 10.00 EUR). |
| Payment Date | Optional ISO 8601 formatted date string representing when the payment was made (e.g., "2023-12-01"). |
| Payment Type | Optional string describing the payment method (e.g., VISA, PAYPAL, SEPA). Max length: 255 characters. |
| Provider | Optional string indicating the payment provider (e.g., Stripe). Max length: 255 characters. |
| Reference | Optional payment reference string for tracking purposes. Max length: 255 characters. |
| Notice | Optional internal note or comment about the payment. |
| Is Overdue Fee | Optional boolean flag indicating if the payment is related to an overdue fee. |
| Mark as Paid (if partial) | Optional boolean flag to mark the document as paid even if the payment amount is less than the total due. |
Output
The node outputs a JSON array containing the response(s) from the Easybill API after creating the payment(s). Each item in the output corresponds to a created payment object with details as returned by Easybill.
No binary data output is produced by this node.
Dependencies
- Requires an active Easybill API credential configured in n8n to authenticate requests.
- Relies on Easybill's API endpoints to create document payment records.
- Uses internal helper functions and endpoint handlers bundled within the node code to interact with the API.
Troubleshooting
- Invalid Document ID: If the document ID is not numeric or does not exist, the node may throw an error. Ensure the document ID is correct and exists in Easybill.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key or token is correctly set up in n8n credentials.
- Amount Issues: Providing zero or negative amounts may result in errors or rejected payments. Always specify a positive integer amount in cents.
- Date Format: The payment date must be in ISO 8601 format. Incorrect formats may cause validation errors.
- API Limits or Downtime: If Easybill API is unreachable or rate-limited, the node will fail. Check network connectivity and API status.
- Partial Payment Flag: Using "Mark as Paid" incorrectly might cause inconsistencies in document status. Use carefully according to business rules.
Links and References
- Easybill API Documentation (general reference for API endpoints and data models)
- ISO 8601 Date Format (for formatting payment dates)