Actions39
- Client Actions
- Loan Actions
Overview
This node integrates with the Fineract API to manage loans and clients. Specifically, for the Loan resource and Goodwill Credit operation, it allows users to apply a goodwill credit transaction to an existing loan. This is useful in scenarios where a lender wants to grant a credit adjustment or concession on a loan balance as a gesture of goodwill, such as waiving fees or providing a payment credit.
Practical examples include:
- Applying a goodwill credit after customer service negotiations.
- Adjusting loan balances due to errors or special circumstances.
- Recording non-standard payments that benefit the borrower without affecting normal payment schedules.
Properties
| Name | Meaning |
|---|---|
| Loan ID | The unique identifier of the loan to which the goodwill credit will be applied. |
| Transaction Date | The date when the goodwill credit transaction occurs, formatted as YYYY-MM-DD. |
| Transaction Amount | The monetary amount of the goodwill credit to be applied to the loan. |
| Payment Type ID | (Optional) Identifier for the type of payment associated with the goodwill credit. |
| External ID | (Optional) An external reference ID for tracking the goodwill credit transaction. |
| Note | (Optional) A textual note describing details or context about the goodwill credit. |
Output
The node outputs JSON data representing the result of the goodwill credit transaction applied to the specified loan. This typically includes confirmation details such as transaction identifiers, status, and any relevant metadata returned by the Fineract API.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a Fineract API instance.
- Needs an API authentication credential configured in n8n with base URL and tenant ID.
- The node sends requests to the
/fineract-provider/api/v1endpoint with appropriate headers including tenant identification and content type.
Troubleshooting
Common issues:
- Invalid or missing Loan ID can cause the API to reject the request.
- Incorrect date format for Transaction Date may lead to validation errors.
- Insufficient permissions or incorrect API credentials will result in authorization failures.
- Providing invalid Payment Type ID or External ID might cause the API to ignore those fields or return errors.
Error messages:
- "Loan not found" — Verify the Loan ID is correct and exists in the system.
- "Invalid date format" — Ensure the Transaction Date is in
YYYY-MM-DDformat. - "Unauthorized" — Check API credentials and tenant configuration.
- "Bad Request" — Review all required fields and their formats.
Resolving these usually involves verifying input values, ensuring proper API credentials, and confirming the loan exists in the Fineract system.
Links and References
- Fineract API Documentation (general reference for endpoints and payloads)
- n8n Documentation (for configuring credentials and using HTTP-based nodes)