> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/time-tracking.md).

# Time Tracking

- [7shifts](https://docs.coupler.io/sources/category/time-tracking/7shifts.md): Connect 7shifts to Coupler.io to export scheduling, time punches, and labor cost data to Google Sheets, BigQuery, or databases automatically.
- [7shifts Best Practices](https://docs.coupler.io/sources/category/time-tracking/7shifts/best-practices.md): Set up separate 7shifts data flows per entity — time punches, users, wages, shifts — then join by user\_id for complete labor analytics.
- [Cal.com](https://docs.coupler.io/sources/category/time-tracking/cal-com.md): Connect Cal.com to Coupler.io and pull booking data, event types, and availability into Google Sheets or BigQuery for scheduling analytics.
- [Cal.com Best Practices](https://docs.coupler.io/sources/category/time-tracking/cal-com/best-practices.md): Join Cal.com bookings and event types to analyze meeting demand, set up multi-user imports, and automate scheduling reports.
- [Clockify](https://docs.coupler.io/sources/category/time-tracking/clockify.md): Sync Clockify time entries, projects, and reports to Google Sheets and BigQuery. Automate Summary, Detailed, and Weekly reports without manual exports.
- [Clockify Best Practices](https://docs.coupler.io/sources/category/time-tracking/clockify/best-practices.md): Start with Summary reports to validate credentials, use macros for rolling dates, and schedule regular refreshes for accurate payroll.
- [Clockodo](https://docs.coupler.io/sources/category/time-tracking/clockodo.md): Pull time entries, projects, and customer data from Clockodo into Google Sheets or BigQuery via Coupler.io for billing and team performance reports.
- [Clockodo Best Practices](https://docs.coupler.io/sources/category/time-tracking/clockodo/best-practices.md): Maximize Clockodo data: use admin API keys to unlock absences and overtime, pair entries with lookup tables for context.
- [Harvest](https://docs.coupler.io/sources/category/time-tracking/harvest.md): Pull time entries, invoices, expenses, and project data from Harvest into Google Sheets or BigQuery via Coupler.io.
- [Harvest Best Practices](https://docs.coupler.io/sources/category/time-tracking/harvest/best-practices.md): Use Time report for dashboards, Time entries for payroll; filter by date range and join multiple entities for complete reports.
- [TimeTonic](https://docs.coupler.io/sources/category/time-tracking/timetonic.md): Export TimeTonic timesheets, project hours, and team activity to Google Sheets, BigQuery, or AI tools via Coupler.io's automated syncs.
- [TimeTonic Best Practices](https://docs.coupler.io/sources/category/time-tracking/timetonic/best-practices.md): Optimize TimeTonic exports with filtered views, date ranges, approved entries, and custom column naming for faster syncs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/time-tracking.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
