Actions39
- Client Actions
- Loan Actions
Overview
The node integrates with the Fineract API to manage loan repayments. Specifically, the "Loan Repay" operation records a repayment transaction against an existing loan in the Fineract system. This is useful for financial institutions or microfinance organizations that want to automate and track loan repayments within their workflows.
Typical use cases include:
- Automatically recording repayments when payments are received through other systems.
- Reconciling loan balances by updating repayments programmatically.
- Integrating loan management into broader business processes such as accounting or customer relationship management.
Properties
| Name | Meaning |
|---|---|
| Loan ID | The unique identifier of the loan for which the repayment is being recorded. |
| Transaction Date | The date when the repayment transaction occurred, formatted as YYYY-MM-DD. |
| Transaction Amount | The amount of money repaid towards the loan. |
| Payment Type ID | Identifier for the type of payment used for the repayment (e.g., cash, bank transfer). |
| External ID | An optional external reference ID for the repayment transaction, useful for reconciliation. |
Output
The node outputs JSON data representing the response from the Fineract API after recording the repayment. This typically includes confirmation details of the repayment transaction such as transaction identifiers, updated loan status, and any relevant metadata returned by the API.
If the node supports binary data output, it would generally relate to attachments or documents associated with the repayment, but this is not indicated in the provided code or properties.
Dependencies
- Requires connection to a Fineract API instance.
- Needs an API key credential configured in n8n with base URL and tenant ID for authentication.
- The node sends requests to the endpoint under
/fineract-provider/api/v1with appropriate headers including tenant identification and content type.
Troubleshooting
Common issues:
- Invalid or missing Loan ID will cause the API to reject the repayment request.
- Incorrect date format for Transaction Date may result in validation errors.
- Insufficient permissions or incorrect API credentials can lead to authentication failures.
- Providing a non-existent Payment Type ID might cause the API to return an error.
Error messages:
- "Loan not found" indicates the specified Loan ID does not exist.
- "Invalid date format" suggests the Transaction Date was not properly formatted.
- "Unauthorized" or "Authentication failed" means the API credentials need verification.
Resolutions:
- Verify all required fields are correctly filled and formatted.
- Check API credentials and tenant configuration.
- Confirm that referenced IDs (loan, payment type) exist in the Fineract system.