> 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/7shifts.md).

# 7shifts

7shifts is a restaurant workforce management platform built for scheduling, time tracking, and labor cost control. Managers use it to publish shift schedules, track employee clock-ins and clock-outs, manage roles and wages across multiple locations, and keep their teams organized. By connecting 7shifts to Coupler.io, you can automatically export your scheduling and time-tracking data to spreadsheets, BI tools, or databases — without manual exports or custom API work.

Coupler.io's 7shifts integration connects via **OAuth** and supports 13 data entities covering your full organizational structure, employee roster, shift schedules, time punch records, and pre-aggregated labor reports.

## Why connect 7shifts to Coupler.io?

* **Automate payroll data exports** — Pull time punch records on a schedule so your payroll team always has accurate clock-in and clock-out data, broken down by employee, role, and location.
* **Track labor costs vs. scheduled hours** — Combine shifts and wages data in a spreadsheet or BI tool to compare scheduled vs. actual labor hours across locations and departments.
* **Build scheduling dashboards** — Export shift and assignment data to analyze coverage gaps, open shifts, and workload distribution over time.
* **Flexible destinations** — Export to AI tools, Google Sheets, Excel, BigQuery, Looker Studio, or other supported destinations.

## Prerequisites

Before connecting, make sure you have:

* A **7shifts** account. Admin or manager-level access is recommended to ensure full data access across all locations and departments.
* A Coupler.io account.

## Quick start

{% hint style="success" %}
Start with the **Time punches** entity. Set the Start date to the first day of your current pay period using the date picker, then run the import and verify the hours look correct for a few employees. Once confirmed, set up a daily auto-refresh to keep your payroll data current automatically.
{% endhint %}

## How to connect

7shifts uses **OAuth authentication** — you sign in with your 7shifts account directly.

{% stepper %}
{% step %}
In Coupler.io, create a new **data flow** and select **7shifts** as the source.\
Click **Connect** and complete the OAuth login with your 7shifts credentials.
{% endstep %}

{% step %}
Grant Coupler.io permission to access your account data.
{% endstep %}

{% step %}
Select a **data entity** from the dropdown. Each data flow exports one entity at a time — for example, **Time punches** for payroll data, **Shifts** for schedule analysis, or **Users** for your employee roster.
{% endstep %}

{% step %}
Set the **Start date** using the date picker. Coupler.io pulls data from this date onwards. For time punches, use the first day of your current pay period. For historical shift data, choose a date that covers your analysis window.
{% endstep %}

{% step %}
Choose your **destination** and run the import.
{% endstep %}
{% endstepper %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.