Your Sentrifugo server already tracks leave, runs appraisals, and manages recruitment. The vibe-code agent in your Open WebUI chat can work that system for you — reading the app’s configuration, querying its MySQL database, and running commands on the server. You type the request in plain language; it does the clicking, checking, and fixing, and shows its work. Here are ten everyday HR jobs you can simply hand over, with the phrases to type.
1. Approve a Leave Request That’s Stuck in Limbo
Leave requests in Sentrifugo wait on the reporting manager, and approvals stall when a manager travels or just gets busy. Instead of clicking through Leave Management screens, ask the agent to find everything pending and act on it. It reads the leave tables, applies your policy, and marks requests approved or declined — then tells you exactly what it changed, with the request IDs so you can spot-check. Try: “Show me all leave requests pending for more than five days, approve the ones under three days, and remind the approvers about the rest.”
2. Load Next Year’s Public Holidays Into a Holiday Group
Every employee in Sentrifugo belongs to a holiday group, and that group’s holiday dates decide which days are blocked from leave. Typing a year of dates into the admin UI is slow and error-prone. The agent can add the dates in one pass and then verify that every active employee sits in the right group. Say: “Add these twelve 2027 public holidays to the HQ holiday group, then check that no active employee is still attached to the old 2024 group.”
3. Create a New Leave Type With Real Rules
Companies invent leave types constantly — work from home, study leave, comp time. Sentrifugo leave types carry real rules: how many days per period, whether a document must be attached, and whether the request draws down a balance. The agent creates the type, sets the limits you describe, and confirms it appears in the employee leave form. Try: “Create a leave type called ‘Work From Home’ that allows two days per month, needs no attachment, and doesn’t reduce the annual leave balance.”
4. Onboard a New Hire End to End
Onboarding touches several modules at once: the employee record, a user login, the right role, a holiday group, a reporting manager, and leave entitlements. That’s five admin screens minimum, and a mistake anywhere shows up weeks later. Give the agent the details once and it chains the steps, catching the classic failure — a missing reporting manager, which silently breaks leave approvals. Say: “Onboard Priya Sharma starting Monday: Marketing department, reports to David Lee, HQ holiday group, standard 21 days of annual leave — and confirm her login works.”
5. Fix a Broken Reporting Line
When someone changes teams, three things must move together: their department, their reporting manager, and the approval chain that depends on both. Done halfway, their leave requests keep routing to the old manager forever. The agent updates the record and then traces a test leave request through the new chain to prove it lands in the right inbox. Try: “Move Alex from Sales to Customer Success, make Sam his reporting manager, and verify his next leave request routes to Sam.”
6. Rescue a Locked-Out User
Logins fail for boring reasons: a wrong password saved in a browser, a stale session, an account flag. The agent can inspect the user record, reset the password, clear whatever is blocking the account, and read the server log to tell you whether it was a typo or someone probing the login page. That last part matters more than it sounds: a slow stream of failed attempts from one IP is often the first sign of someone probing your HR data. Say: “Maria can’t log in — reset her password, clear anything that’s blocking her, and tell me if there were failed login attempts from strange IPs.”
7. Produce a Leave Balance Report for Payroll
At month end, payroll wants numbers in a file, not screenshots of admin screens. The leave summary tables hold each employee’s balance per leave type, but the built-in views don’t always match the layout finance asks for. The agent queries the data, shapes it to the requested columns, and hands you a spreadsheet. Try: “Give me a CSV of annual leave balances for the Engineering department, sorted by reporting manager, that I can open in Excel.”
8. Post an Announcement People Actually See
Sentrifugo announcements sit inside the app, and employees forget the app exists. The agent can post the announcement in Sentrifugo and push the same text out by email so nobody misses it, then check the mail log and list anyone whose address bounced. One request covers both channels. Say: “Post an announcement that the office closes at noon on Friday, email it to everyone, and list anyone whose email bounced.”
9. Diagnose Why Emails Aren’t Sending
Interview confirmations and leave decisions both depend on mail getting out, and Sentrifugo’s scheduled mail only flows if its cron job is actually running — something that quietly breaks after server maintenance. When a candidate says they never received a confirmation, the agent can check the SMTP settings, test the cron, read the mail log, and fix what it finds. Most of the time it’s the cron line missing from the crontab or an SMTP password rotated last quarter — both quick to confirm and quick to fix. Try: “Candidates aren’t receiving interview confirmation emails — figure out why and fix it.”
10. Tidy Up the Recruitment Pipeline
Old requisitions and rejected candidates pile up until the recruitment dashboard is unreadable and nobody trusts it. Closing what you already hired for, archiving the rest, and leaving active searches untouched is careful, repetitive cleanup — exactly what an agent is good at. It reports a short summary when done. Say: “Close every requisition we hired for last quarter and archive its rejected candidates, but leave anything still active alone.”
None of these require you to learn Sentrifugo’s admin screens. Type the request, watch the agent work, and ask it to explain anything that looks surprising. Get Sentrifugo preinstalled on your own server with the agent ready in the chat: Sentrifugo on OpenSysLab.
