Actions39
- Client Actions
- Loan Actions
Overview
This node integrates with the Fineract API, specifically to manage clients and loans. The "Client - Reject" operation allows users to reject a client in the Fineract system by specifying the client's ID along with optional details such as the rejection date and reason. This is useful in scenarios where a client application or profile needs to be declined or marked as rejected based on business rules or compliance checks.
Practical examples include:
- Automatically rejecting loan applicants who do not meet certain criteria.
- Marking clients as rejected after manual review within an automated workflow.
- Scheduling client rejections effective from a specific date.
Properties
| Name | Meaning |
|---|---|
| Client ID | The unique identifier of the client to reject (required). |
| Rejection Date | The date when the client should be rejected, formatted as YYYY-MM-DD (optional). |
| Rejection Reason ID | Numeric ID representing the reason for rejecting the client (optional). |
Output
The node outputs JSON data reflecting the response from the Fineract API after attempting to reject the specified client. This typically includes confirmation of the rejection action or details about the updated client status. There is no indication that binary data is output by this node.
Dependencies
- Requires connection to a Fineract API instance.
- Needs an API key credential with appropriate permissions to manage clients.
- Requires configuration of base URL and tenant ID for the Fineract platform in the node credentials.
Troubleshooting
- Invalid Client ID: If the provided client ID does not exist, the API will likely return an error indicating the client was not found. Verify the client ID before running the node.
- Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Ensure the API key and tenant ID are correctly configured.
- Date Format Issues: The rejection date must be in
YYYY-MM-DDformat. Incorrect formatting may lead to request rejection. - Permission Denied: The API user must have rights to reject clients; otherwise, the operation will fail.
- API Endpoint Unreachable: Network issues or incorrect base URL settings can prevent communication with the Fineract API.
Links and References
- Fineract API Documentation (general reference for API endpoints and usage)
- n8n Documentation (for general guidance on using custom nodes and credentials)