Actions39
- Client Actions
- Loan Actions
Overview
The node integrates with the Fineract API to update client information. It allows users to modify details of an existing client in the Fineract system, such as their name, contact information, office assignment, and status. This is useful in scenarios where client data needs to be kept current, for example, updating a client's mobile number or marking a client as inactive.
Practical examples:
- Updating a client’s email address after they provide a new one.
- Changing the office assignment of a client when they move locations.
- Marking a client as inactive if they are no longer active in the system.
Properties
| Name | Meaning |
|---|---|
| Client ID | The unique identifier of the client to update (required). |
| First Name | Client's first name. |
| Last Name | Client's last name. |
| Office ID | Numeric ID of the office where the client belongs. |
| Active | Boolean indicating whether the client is active. |
| Mobile Number | Client's mobile phone number. |
| Email Address | Client's email address. |
| External ID | An external identifier associated with the client. |
Output
The node outputs JSON data representing the updated client record as returned by the Fineract API. This typically includes all client fields after the update operation, reflecting the new state of the client in the system.
If the node supports binary data output, it is not indicated here; the primary output is structured JSON data.
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 API endpoint
/fineract-provider/api/v1.
Troubleshooting
- Common issues:
- Invalid or missing Client ID will cause the update to fail.
- Incorrect API credentials or base URL will result in authentication errors.
- Providing invalid data types (e.g., string instead of number for Office ID) may cause request rejection.
- Error messages:
- Authentication errors usually indicate misconfigured API credentials.
- "Client not found" errors suggest the Client ID does not exist in the system.
- Validation errors from the API indicate incorrect or missing required fields.
To resolve these:
- Verify that the Client ID exists and is correct.
- Check API credentials and ensure the base URL and tenant ID are properly set.
- Validate input data types and required fields before executing the node.
Links and References
- Fineract API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding API calls)
- Fineract GitHub Repository