Jibble

Pull time tracking data from Jibble. Agents list people, groups, activities, and locations, read individual time entries, and build timesheet summaries for payroll prep and attendance reporting.

8 actions OAuth available

Jibble website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

The weekly payroll prep window opens on a schedule

Get Timesheet Summary pulls each person's tracked, overtime, and break hours for the week

List Time Entries spot-checks the raw punches behind any summary that looks off, like a 16-hour day or a missing out-punch

List People confirms the roster, so leavers and new joiners are handled explicitly

The payroll reviewer clears the flagged anomalies before hours become wages

Approved totals append to the payroll spreadsheet

The operations channel gets the week's summary with overtime names called out

What This Integration Enables

Jibble's punch clock produces the most consequential dataset in an hourly operation, because those timestamps become wages and invoices. This connector is deliberately read-only: FlowRunner agents pull people, groups, activities, and locations for context, read raw clock-in and clock-out entries with OData filtering by person and date range, and fetch Jibble's own rolled-up timesheet summaries with tracked, overtime, and break hours per period. The punches stay untouched at the source; what the agents automate is everything downstream of them. - Export tracked hours or raw punches into [Google Sheets](/integrations/google-sheets) for payroll reconciliation - Pull weekly or monthly per-person summaries for reporting without building the aggregation yourself - Bill clients from tracked time by feeding filtered entries into [QuickBooks Online](/integrations/quickbooks) invoices - Alert ops in [Slack](/integrations/slack) when someone crosses an overtime threshold - Enrich other automations with attendance context: who was on site, at which location, on which activity A useful design note: use Get Timesheet Summary when you need rolled-up hours and List Time Entries when a number needs defending, because the raw punches are the evidence behind every total. The OData query surface makes both efficient: server-side filters by person, role, and date range mean flows pull exactly the slice they need instead of exporting the workspace and filtering in a spreadsheet, and paging through large teams is a cursor, not a download.

Without FlowRunner

Payroll prep starts with an export Someone downloads punches, builds pivot tables, and hunts anomalies by eye

Overtime is discovered at payday The threshold was crossed on Tuesday; finance finds out with the pay run

Billable hours leak Client work gets tracked in Jibble but never fully makes it onto an invoice

With FlowRunner

Payroll prep starts from a summary Tracked, overtime, and break totals arrive per person, already aggregated by Jibble

Overtime alerts fire mid-week Anyone over threshold gets flagged to ops while the schedule can still respond

Tracked time becomes invoices Entries filtered by client and date range flow into billing with nothing dropped

Use Case Scenarios

Payroll prep as a Monday morning artifact

At 7 am Monday, the flow runs Get Timesheet Summary with Weekly granularity for last week's anchor date. Per-person totals append to the payroll tab in [Google Sheets](/integrations/google-sheets). Any summary with overtime, or a day exceeding twelve tracked hours, gets its raw punches pulled via List Time Entries and attached as evidence rows. The payroll reviewer opens one sheet with the anomalies pre-flagged instead of an export and a blank pivot table.

Tracked time that turns into revenue

Client work is tracked against activities in Jibble. At month end, the agent runs List Time Entries filtered by the client's activity and the billing period, resolves names through List People, totals the hours, and stages an invoice in [QuickBooks Online](/integrations/quickbooks) with the time detail as line items. The billing manager reviews and sends. Hours that used to evaporate between the punch clock and the invoice now arrive itemized.

The overtime alarm that rings on Wednesday

A midweek sweep runs Get Timesheet Summary with Daily granularity across the current week. Anyone trending past their overtime threshold posts to the operations channel in [Slack](/integrations/slack) with name, hours so far, and remaining scheduled shifts. The ops lead rebalances Thursday and Friday instead of explaining the overtime line to finance next week.

Human-in-Loop Highlight

Get Timesheet Summary returns numbers that are about to become money: the tracked and overtime totals it reports flow directly into payroll runs and client invoices, and the punches beneath them are entered by humans who forget to clock out, clock in twice, and work through breaks. This connector cannot damage Jibble, it is read-only by design, but a flow that pipes its output straight into wages or a [QuickBooks Online](/integrations/quickbooks) invoice can absolutely damage a paycheck or a client relationship. So the human gate in every Jibble flow sits at the conversion point. The agent aggregates, cross-checks summaries against raw entries from List Time Entries, and flags what does not reconcile: the 19-hour Tuesday, the week with tracked time but no location, the summary that disagrees with its own punches. The payroll reviewer or billing manager clears the flags, and only cleared numbers become dollars. Underpay someone, or overbill a client, and the correction costs far more than the review ever does.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

8 actions

People

List People Lists workspace members with OData filtering, ordering, and paging, returning id, name, email, role, and status. The roster read that anchors payroll sweeps and billing name resolution.
Get Person Retrieves a single member by id, optionally expanding related entities such as their group. The lookup behind per-person reports and escalations.

Groups

List Groups Lists the workspace's teams, used to organize members and scope reports. The structure read for grouping summaries by department.

Activities

List Activities Lists the activities members select when clocking in, such as project or task names. The key that maps tracked time to clients and billable work.

Locations

List Locations Lists the kiosks and geofenced sites configured for on-site attendance. The context read for site-level attendance reporting.

Time Tracking

List Time Entries Lists raw clock-in and clock-out punches with person, timestamp, activity, and location, filterable by person and date range. The evidence layer: when a total needs defending, these are the receipts.
Get Time Entry Retrieves a single punch by id with its person, In or Out type, timestamp, activity, and location, optionally expanded. The drill-down for investigating one anomalous event.
Get Timesheet Summary Returns Jibble-computed totals for tracked hours, overtime, and breaks at Daily, Weekly, or Monthly granularity for the period containing an anchor date. The aggregated read behind payroll prep and overtime alerts, and the number a human clears before it becomes money.

Frequently Asked Questions

What can FlowRunner do with Jibble?

FlowRunner agents can run List People, Get Person, and List Groups in Jibble, plus 5 more actions.

Does connecting Jibble to FlowRunner require OAuth?

Yes. Jibble connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Jibble trigger a FlowRunner workflow automatically?

Jibble doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Jibble

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us