Actions39
- Client Actions
- Loan Actions
Overview
The node integrates with the Fineract API to manage loans, specifically enabling the "Write Off" operation on a loan. Writing off a loan typically means marking it as uncollectible and removing it from active receivables. This node is useful in financial workflows where loan portfolios are managed, allowing automation of loan status updates directly through the API.
Practical examples include:
- Automatically writing off loans that have been delinquent beyond a certain threshold.
- Integrating loan write-off actions into broader client management or accounting processes.
- Recording write-off transactions with relevant metadata such as transaction date, amount, and notes for audit trails.
Properties
| Name | Meaning |
|---|---|
| Loan ID | The unique identifier of the loan to be written off. |
| Transaction Date | The date when the write-off transaction occurs, formatted as YYYY-MM-DD. |
| Transaction Amount | The monetary amount to write off from the loan balance. |
| External ID | An optional external reference identifier for the write-off transaction. |
| Note | An optional note or comment describing the write-off transaction. |
Output
The node outputs JSON data representing the response from the Fineract API after performing the write-off operation. This typically includes confirmation details of the transaction such as updated loan status, transaction identifiers, timestamps, and any messages returned by the API.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Fineract API.
- Needs configuration of the base URL and tenant ID for the Fineract platform within n8n credentials.
- 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 request.
- Incorrect date format for Transaction Date may result in validation errors.
- Insufficient permissions or incorrect API credentials can lead to authentication failures.
- Writing off an amount greater than the outstanding loan balance might be rejected by the API.
Error messages:
- "Loan not found" — Verify the Loan ID is correct and exists in the system.
- "Invalid transaction date" — Ensure the date is in
YYYY-MM-DDformat. - "Unauthorized" — Check API credentials and tenant configuration.
- "Amount exceeds outstanding balance" — Adjust the transaction amount accordingly.
Resolving these usually involves verifying input parameters, ensuring proper credential setup, and confirming the loan's current state in the Fineract system.
Links and References
- Fineract API Documentation (general reference for API endpoints and data models)
- n8n Documentation (for configuring credentials and using custom nodes)