GIRITON
HRConnect AI agents to GIRITON, a Czech attendance and time tracking HR system. Agents update employees, record attendance events, add vacations, and process attendance requests so time data reaches payroll without manual chasing.
What This Integration Enables
GIRITON is a Czech attendance and time tracking system, and its API tells you immediately what kind of workforce it was built for. You can address a person by database ID, personnel number, email, or attendance card ID. That last one is the tell. This is a system where people badge in at a terminal on a shop floor or a site entrance, not one where knowledge workers set their own hours in a browser tab. Get Users Activity returns who is currently working, when they arrived, and what attendance errors they have accumulated today. The platform computes daily and monthly results, and the disputes it produces land in a request queue that somebody has to work through.
FlowRunner agents cover that pipeline end to end. On people they list employees with a valid employment on a given day, read a full profile including job position and salary, create or update a person through a single upsert, and email a new starter an invitation to activate their login. They list and upsert departments with their hierarchy. On attendance they pull data for many employees or one, scoped by people, departments, or tags, choosing which sections to include: raw records, shift plan, daily results, monthly results. They read live presence for a chosen day, record a clock in or clock out for a named activity, and add a vacation across a date range with options to skip weekends and holidays or to insert only on planned shift days. On planning they read the shift plan for selected people and list the shift templates the account defines. On approvals they list attendance requests filtered by state and type, then approve, deny, or delete one. Two further operations manage permission groups and their membership.
Two behaviors deserve attention before you give an agent write access. Add or Update Employee matches on the database ID or the personnel number, so an incorrect number does not fail loudly. It updates a different real person. And Add Permission Group Members grants a group's permissions to the employees you pass in, which in an attendance system means visibility into colleagues' presence, attendance errors, and profile data including salary. Neither is a reason to avoid automation. Both are reasons to place the human-in-the-loop step at the write, not after it. Access is via an API token in the giriton-token header, generated in the GIRITON web app under Paired devices.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Period Close Without the Floor Walk
Two days before the attendance period closes, the agent runs Get Attendance Data for each department across the period with raw records and daily results included, then reads Get Shift Plan for the same people. Days where the recorded time and the planned shift disagree get pulled out. Before calling any of them unexplained, the agent runs List Attendance Requests, because a gap covered by a pending vacation request is not an error, it is an unanswered request. What reaches the approver is one list per person: open requests first, then genuine gaps with the badge times on record. The approver works through it once. The agent writes the decisions with Change Request Status and mirrors the closed period into Xero for payroll.
A New Starter Who Can Badge In on Day One
A signed contract lands in the document system. The agent extracts the person's details, resolves their department against List Departments, and runs Add or Update Employee with the employment start date that determines when they become active. It deliberately leaves the Employee ID empty, because supplying one turns a create into an update of whoever holds that ID. Once the record exists, Send Account Invitation emails the new starter the link to create their login, and the agent posts the completed setup to the hiring manager in Microsoft Teams. The person arrives to a working badge and an account instead of a first morning spent at the HR desk.
Live Presence Where It Actually Matters
For sites with a minimum staffing requirement, the agent polls Get Users Activity through the shift and compares who is marked in progress against the shift plan for that day. When a site drops below its required cover, it raises the gap to the duty manager with the names of who is on site, who was planned, and who is showing an attendance error. Nothing is written automatically. This is a presence signal used to prompt a person, not a surveillance feed. GIRITON has no webhooks, so flows here start from a schedule or from an event in another system, and the polling interval is a design choice worth making deliberately rather than setting to the lowest number the rate limits allow.
Human-in-Loop Highlight
Change Request Status does something most approval APIs do not admit to. Its own description says it approves, denies, or deletes a request on behalf of an approver. The record GIRITON keeps will name a human being who may never have seen the request. That is the moment the gate belongs on, because the value of an approval trail is entirely in whether the named person actually decided. So the agent does the gathering and stops short of the verdict. It sends one message: "Jana Novakova, vacation request 12 to 16 May, 5 days. Remaining entitlement 8 days. Two colleagues in the same department are already approved for the 13th and 14th. Approve, deny, or return with a question?" The approver answers, and only then does the agent call Change Request Status carrying that answer. This is the digital andon cord applied to an approval queue. The agent removes the reconciliation work, and the signature stays attached to a person who really signed.
Agent Capabilities
18 actionsEmployees
4- List Employees Return employees with a valid employment on a given day, paginated with offset and limit. Used to sync the directory or resolve a person's database ID.
- Get Employee Return the full profile of one employee by database ID, including contact details, job position, salary, addresses, and department membership.
- Add or Update Employee Create a new employee or update an existing one, matched by database ID or personnel number. Leave the ID empty to create. Only the fields you supply are set.
- Send Account Invitation Email an employee a link to create their GIRITON login and password. Used immediately after a record is created so a new starter can activate their own account.
Departments
2- List Departments Return all departments with hierarchy path, complete name, and hidden status. Used to resolve department IDs before filtering attendance or project queries.
- Add or Update Department Create a new department or update an existing one. Leave the Department ID empty to add.
Attendance
5- Get Attendance Data Return attendance for many employees over a date range, scoped by database IDs, personnel numbers, attendance card IDs, departments, or tags, with a choice of sections including raw records, shift plan, and daily or monthly results.
- Get Person Attendance Data Return attendance for a single employee, identified by database ID, personnel number, email, or attendance card ID.
- Get Users Activity Return each employee's activity for a chosen day, including whether they are currently working, arrival and departure times, and attendance errors. Used for live cover checks.
- Add Attendance Event Record a clock in or clock out for a named activity at a specific time. Supplying an existing event ID updates that event rather than creating a new one.
- Add Vacation Add a vacation across a date range, with options to skip weekends and holidays or to insert only on days with a planned shift.
Projects and Shifts
3- List Projects Return projects valid within a date range, optionally filtered by department, with pagination and an option to include inactive projects.
- Get Shift Plan Return the shift plan for specified employees within a period, scoped by people, departments, or tags. Used as the comparison baseline during a period close.
- List Shifts Return the shift definitions available in the account, optionally filtered by a validity window.
Requests
2- List Attendance Requests Return attendance and shift requests over a date range, filtered by state and type. Used to build the approval queue and to separate covered days from real gaps.
- Change Request Status Approve, deny, or delete an existing request on behalf of an approver. Because the record names that approver, this call belongs after a human decision, not before one.
Permission Groups
2- List Permission Groups Return the permission groups defined in the account with their name, description, and tags.
- Add Permission Group Members Add one or more employees to a permission group by database ID. In an attendance system this grants visibility into other people's data, so treat it as an access change rather than a record update.
Frequently Asked Questions
What can FlowRunner do with GIRITON?
FlowRunner agents can run List Employees, Get Employee, and Add or Update Employee in GIRITON, plus 15 more actions.
Does connecting GIRITON to FlowRunner require OAuth?
No. GIRITON connects to FlowRunner with an API key, no OAuth flow required.
Can GIRITON trigger a FlowRunner workflow automatically?
GIRITON doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with GIRITON
$100 in credits. No card required. Connect in minutes.