Timeero logo

Timeero

Time Tracking

GPS time tracking for field crews: Ruby can total labor hours, see who is clocked in, and read schedules and mileage.

17 tools
API KEY
Read-only

Ask Ruby

“Who's clocked in right now and which job are they on?”
“Total hours by employee for last week's pay period.”
“How many labor hours and miles went into the Maple St job?”
“Who's scheduled tomorrow, and is anyone off?”
What Ruby can do

17 read-only tools

Ruby reads from Timeero and grounds her answers in your data. Every tool is read-only: she surfaces, summarizes, and drafts; a human always takes the action.

List users

List employees List the company's employees (crew members, supervisors, admins) with their role, pay rate, active status, and whether location and mileage tracking is enabled. Deleted users are not returned.

Get user

Get one employee Get a single employee's full record by user id: name, contact details, role, pay rate, tracking settings, and custom fields. (GET /users/{id})

List groups

List groups List the company's groups (crews, departments, or locations that employees are organized into). Group ids feed the group_id filter on users and timesheets.

Get group

Get one group Get a single group's information (name and members) by group id. (GET /groups/{id})

List jobs

List jobs List the company's jobs. In Timeero a job is whatever crews clock into: a customer, a loss address, a project, or a vehicle. Includes hourly rate, geofence settings, and active status. Job ids feed the job_id filter on timesheets and schedules.

Get job

Get one job Get a single job by id, including its custom geofence coordinates, hourly rate, mileage-tracking setting, and contact details. (GET /jobs/{id})

List tasks

List tasks List the tasks employees can clock into within a job (e.g. demo, water extraction, drying, packout).

Get task

Get one task Get a single task's information by task id. (GET /tasks/{id})

List timesheets

List timesheets (hours worked, by date range, employee, or job) The core labor-hours endpoint. Each entry carries the employee, job and task, clock-in/clock-out times and timezones, clock-in/out addresses and GPS coordinates, total hours, mileage driven, break count, flagged status, and approval state. Use it for payroll periods, job costing (labor hours and mileage per job), and per-employee productivity.

Get timesheet

Get one timesheet Get a single timesheet entry by id, with its full clock-in/out detail, mileage, breaks, and custom fields. (GET /timesheets/{id})

List schedules

List schedules (planned shifts) for a date range List planned shifts: who is scheduled for which job, when, and whether the shift is still a draft or published to the crew. Use it for dispatch questions about tomorrow or next week. The date_range parameter is REQUIRED.

Get schedule

Get one schedule Get a single scheduled shift by id, including its assigned employee, job, times, repeat configuration, and notes. (GET /schedules/{id})

Why connect it to Ruby

Built for restoration, not bolted on.

Grounded answers

Ruby reads Timeero live and cites what she found, so answers reflect your actual data, not a stale export.

Read-only by design

Least-privilege, read-only access. Ruby surfaces and drafts; your team always takes the action.

Managed, secure auth

Connect with one click. Tokens are encrypted and scoped per company; revoke access any time.

Knows restoration

Ruby understands jobs, claims, drying logs, and AR, so Timeero data lands in the right operational context.

Use it from anywhere

Connect once, then just ask.

Connect Timeero once in Ruby. Ask in the Ruby app, or bring the same secure connection into the assistant your team already uses.

Ruby

Ask in the Ruby app and get an answer grounded in Timeero and the rest of your connected stack.

Claude

Bring the same secure Timeero connection into Claude so it can answer with your live data.

ChatGPT

Use Timeero from ChatGPT with the same per-company, read-only access Ruby uses.

Frequently asked questions

Do I need developer credentials to connect Timeero?

You paste an API key from your account in Settings > Integrations. There is nothing to build; Ruby stores it encrypted and scoped to your company.


Can Ruby change anything in Timeero?

No. The Timeero connection is read-only. Ruby reads, summarizes, and drafts; a human always makes the change in Timeero.


Is my Timeero data secure?

Credentials are encrypted at rest and access is scoped per company. You can revoke the connection at any time from Settings > Integrations, which immediately cuts Ruby off.


Can I use Timeero alongside my other tools?

Yes. Ruby reasons across every tool you connect at once, so she can tie Timeero to your CRM, accounting, email, and documentation in a single answer.