---
title: "Good to know about Clockify"
slug: "good-to-know-about-clockify"
description: "Learn more about request limits, historical range, and things to consider when using the Supermetrics Clockify connector."
updated: 2026-09-10T07:22:52Z
published: 2026-09-10T07:22:52Z
canonical: "docs.supermetrics.com/good-to-know-about-clockify"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.supermetrics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Good to know about Clockify

This article outlines recommendations and notes certain limitations imposed by the data source API, which you may need to consider when building your queries.

If you’re connecting to Clockify, follow the instructions in our [connection guide](/v1/docs/clockify-connection-guide). See [Clockify metrics and dimensions](/v1/docs/clockify-fields) for the fields available in this data source.

## Request limits and recommended refresh rate

**Request limit**: 10 requests per second.

**Recommended refresh window**: 2-3 days.

## Historical range

There are no known limitations to the historical range of data you can pull with the Clockify data source connector.

## Accounts in Clockify

In the Clockify connector, each Account is considered a separate account within the connection.

Your Supermetrics subscription determines the number of [data source accounts](/v1/docs/about-data-source-accounts) you can use simultaneously.

## Things to consider

### Time zone mismatch

A mismatch between the destination time zone and the native Clockify time zone settings will cause the date to be displayed incorrectly at the destination.

## More resources

- [Clockify connection guide](/v1/docs/clockify-connection-guide)
- [Clockify report building guide](/v1/docs/clockify-report-building-guide)
- [Clockify metrics and dimensions](/v1/docs/clockify-fields)