What this operation supports in Jibble
Call this method when you need to capture a user’s work start or end times within the Jibble ecosystem. This integration ensures accurate presence tracking for teams using Jibble’s timekeeping capabilities.
Request behavior and expectations
Jibble processes the clock action and returns a time-stamped acknowledgment. The operation contributes to accurate timesheets and project labor reporting in Jibble.
Operational considerations
Identifiers such as user_id or person_id are used to associate the clock action with a Jibble entity. Execution order matters to reflect correct daily work periods in Jibble’s UI.
Use cases
Overview of practical automation scenarios involving Jibble's clock actions.
- Automatically clock in a remote technician when a support session starts, then clock out on ticket completion, all under Jibble’s audit trail.
- Sync a calendar event’s start and end with Jibble to reflect on-site work durations in timesheets.
- Trigger clock in/out from an HRIS event to align payroll windows within Jibble.
- Capture break periods by clocking out, then resume with a subsequent clock in in Jibble.