LEDGERS icon

LEDGERS

Interact with LEDGERS API
Join our community

Actions34

Overview

This node allows updating employee details in an HRMS (Human Resource Management System) specifically for India. It is useful for automating the process of modifying employee records such as personal information, employment status, bank details, and contact information. Typical use cases include updating employee profiles after changes like promotions, transfers, exits, or corrections to personal data.

For example, you can update an employee's designation, department, or bank account details programmatically when integrating your HR system with other tools or workflows.

Properties

Name Meaning
GID The unique identifier (GID) of the employee whose record you want to update. This is a required field.
Update Fields A collection of fields that can be updated for the employee. These include:
- Aadhar Employee's Aadhar number (Indian unique ID).
- Blood Group Employee's blood group. Options: A-, A+, AB-, AB+, B-, B+, O-, O+.
- Branch Name or ID The branch where the employee works. Can be selected from a list or specified by ID via expression.
- Date of Birth Employee's date of birth.
- Date of Exit Date when the employee left the company.
- Date of Join Date when the employee joined the company.
- Department Department name the employee belongs to.
- Designation Job title or designation of the employee.
- Emergency Contact Emergency contact phone number.
- Employee Account Name (Bank) Bank account holder's name.
- Employee Account Number (Bank) Bank account number.
- Employee Account Type (Bank) Type of bank account. Options: Current Account, Salary Account, Savings Account.
- Employee Bank Branch (Bank) Bank branch name.
- Employee Bank Name (Bank) Name of the bank.
- Employee ID Unique employee ID.
- Employee IFSC Code (Bank) Bank IFSC code (Indian banking system).
- Employee Status Employment status. Options: Active, Inactive.
- Employment Type Type of employment. Options: Contract, Freelance, Full Time, Internship, Part Time.
- Exit Description Reason or description for employee exit.
- Father Name Father's name of the employee.
- Gender Gender of the employee. Options: Female, Male, Other.
- Marital Status Marital status. Options: Divorced, Married, Single, Widowed.
- Name Full name of the employee.
- Office Email Official email address.
- Office Mobile Official mobile phone number.
- PAN PAN card number (Indian tax ID).
- Permanent Address Permanent address details including multiple addresses with fields: Address Line 1, Address Line 2, City, Country, Pincode, State.
- Personal Email Personal email address.
- Personal Mobile Personal mobile phone number.
- Present Address Present address details similar to permanent address structure.
- Religion Religion of the employee.
- Reporting Name or ID The manager or reporting person for the employee. Can be selected from a list or specified by ID via expression.
- Shift Timing Work shift timing in format HH:MM:SS-HH:MM:SS.
- UAN Number Universal Account Number for Provident Fund (PF) in India.

Output

The node outputs JSON data representing the updated employee record as returned by the HRMS API. This typically includes confirmation of the updated fields and possibly the full employee object after modification.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication with the HRMS backend service.
  • Needs valid credentials including API key, email, password, and API URL configured in n8n.
  • Uses HTTP requests to communicate with the HRMS API endpoints.
  • Some properties load options dynamically by calling API methods (e.g., branches, employees for reportingTo).

Troubleshooting

  • Authentication errors: If login fails, check that the API key, email, and password credentials are correct and have sufficient permissions.
  • Invalid GID: Ensure the GID provided corresponds to an existing employee; otherwise, the update will fail.
  • Field validation errors: Some fields may require specific formats (e.g., dates, shift timing). Invalid formats may cause API errors.
  • Empty or missing update fields: If no update fields are provided, the node might not perform any action or return an error.
  • API rate limits or connectivity issues: Network problems or API throttling could cause request failures; retry or check network settings.

Links and References

  • n8n Expressions Documentation — for using expressions in property values.
  • Indian HRMS and payroll regulations references (for understanding fields like UAN, PAN, Aadhar).
  • Generic REST API usage guides for troubleshooting HTTP request issues.

Discussion