Actions39
- Client Actions
- Loan Actions
Overview
This node integrates with the Fineract API to manage loan recovery payments. It allows users to record a recovery payment transaction against a specific loan by providing details such as the loan ID, transaction date, amount, payment type, and optional notes or external identifiers.
Common scenarios include:
- Recording repayments made by clients on their loans.
- Tracking recovery payments for accounting or auditing purposes.
- Automating loan management workflows where repayment data needs to be synchronized with Fineract.
Practical example:
A financial institution uses this node in an automation workflow to log every loan repayment received from clients into their Fineract system, ensuring that loan balances are updated accurately and timely.
Properties
| Name | Meaning |
|---|---|
| Loan ID | The unique identifier of the loan for which the recovery payment is being recorded. |
| Transaction Date | The date when the recovery payment transaction occurred (format: YYYY-MM-DD). |
| Transaction Amount | The monetary amount of the recovery payment. |
| Payment Type ID | Identifier specifying the type of payment made (e.g., cash, bank transfer). |
| External ID | An optional external reference ID for the recovery payment transaction. |
| Note | Optional note or comment related to the recovery payment transaction. |
Output
The node outputs JSON data representing the response from the Fineract API after recording the recovery payment. This typically includes confirmation details of the transaction such as IDs, status, timestamps, and any metadata returned by the API.
No binary data output is involved.
Dependencies
- Requires connection to a Fineract instance via its REST API.
- Needs an API authentication credential configured in n8n with:
- Base URL of the Fineract server.
- Tenant ID for multi-tenant environments.
- An API key or token for authorization.
- The node sends requests with appropriate headers including content type and tenant identification.
Troubleshooting
- Invalid Loan ID: If the provided loan ID does not exist or is incorrect, the API will return an error. Verify the loan ID before submitting.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token and tenant ID are correctly set.
- Date Format Issues: The transaction date must be in YYYY-MM-DD format. Incorrect formats may lead to request rejection.
- Missing Required Fields: Omitting required properties like loan ID, transaction date, or amount will result in errors. Make sure all mandatory fields are filled.
- API Endpoint Unreachable: Network issues or incorrect base URL configuration can prevent communication with the Fineract server.
Links and References
- Fineract API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding API integrations)