Actions39
- Client Actions
- Loan Actions
Overview
This node integrates with the Fineract API to manage client data, specifically allowing users to close a client account. Closing a client typically means marking their account as inactive or terminated in the system, which is useful for financial institutions managing loan clients or customer records.
Common scenarios include:
- Marking a client as closed after loan repayment completion.
- Deactivating client accounts that are no longer active or have requested closure.
- Archiving client data by setting a closure date and reason.
Practical example:
A loan officer wants to close a client's account on a specific date due to loan settlement. They provide the client ID, specify the closure date, and select a reason for closure. The node sends this information to the Fineract API to update the client's status accordingly.
Properties
| Name | Meaning |
|---|---|
| Client ID | The unique identifier of the client to be closed. |
| Closure Date | The date when the client should be closed, formatted as YYYY-MM-DD. |
| Closure Reason ID | Numeric ID representing the reason for closing the client (e.g., completed loan, etc.). |
Output
The node outputs JSON data reflecting the response from the Fineract API after attempting to close the client. This typically includes confirmation of the closure operation, updated client details, or error messages if the operation failed.
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.
- The node uses HTTP requests to communicate with the Fineract API endpoint
/fineract-provider/api/v1.
Troubleshooting
- Invalid Client ID: If the provided client ID does not exist, the API will return an error. Verify the client ID before running the node.
- Missing Required Fields: The client ID is mandatory; omitting it will cause the node to fail.
- Incorrect Date Format: Ensure the closure date is in
YYYY-MM-DDformat to avoid validation errors. - Unauthorized Access: Check that the API credentials are correct and have sufficient permissions.
- Closure Reason ID Invalid: Use valid reason IDs as defined in your Fineract setup; invalid IDs may cause errors.
Links and References
- Fineract API Documentation (for detailed API endpoints and parameters)
- n8n Documentation (for general usage of custom nodes and credentials)