# Clockify to google sheets

**URL:** <https://community.n8n.io/t/clockify-to-google-sheets/63695>\
**Category:** Questions\
**Tags:** clockify\
**Created:** [December 2, 2024, 8:07am UTC](https://community.n8n.io/t/clockify-to-google-sheets/63695 "2024-12-02T08:07:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vinod\_Kanted](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/vinod_kanted/32/45875_2.png) [@Vinod\_Kanted](https://community.n8n.io/u/Vinod_Kanted)\
**Post date:** [December 2, 2024, 8:07am UTC](https://community.n8n.io/t/clockify-to-google-sheets/63695/1 "2024-12-02T08:07:49Z")

</div>

I am trying to get time entries from clockify to google sheet, But it does not work, Have added a clockify trigger, but Nothing happens,no executionsDono where I am wrong.

## Please share your workflow

```auto
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

```

## Share the output returned by the last node

## Information on your n8n setup

- **n8n version:** 1.61.0
- **Database (default: SQLite):** Default
- **n8n EXECUTIONS\_PROCESS setting (default: own, main):**
- **Running n8n via (Docker, npm, n8n cloud, desktop app):** Docker
- **Operating system:**

---

<div class="post-metadata">

**Author:** ![ria](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/ria/32/99251_2.png) [@ria](https://community.n8n.io/u/ria)\
**Post date:** [December 10, 2024, 2:57pm UTC](https://community.n8n.io/t/clockify-to-google-sheets/63695/2 "2024-12-10T14:57:31Z")

</div>

Hi @Vinod_Kanted

Thanks for sharing this.  
We’re aware that the trigger is broken right now and will hopefully release a PR soon.  
Was also posted on Github:

> <https://github.com/n8n-io/n8n/pull/10803>
>
> \## Summary
> 
> Fixes some aspects of the "new time entry" clockify trigger, as we…ll as adding support for periodically fetching all entries for entry updating workaround. 
> 
> \*\*Problem\*\*: This issue stems from a fundamental problem within the \[Clockify API\](https://docs.developer.clockify.me/#tag/Time-entry/operation/getTimeEntries), which does not allow access to most recent time entry submissions by date submitted (or finalized/created or stopped). Furthermore, Clockify only allows one to retrieve entries through start date (registered by the user) and end date (also inputted by the user) \[plus a bit more irrelevant options\]. The prior code seemed to have been treating the "start date" as submission/stop/finalization date (that's at least what it looks like, not sure if it was intentional), which caused problems such as discarding entries that have start dates prior to the latest checked date (so if it checked a minute ago, it would only fetch items from the current minute, then move onto the next minute). 
> 
> \*\*Solution\*\*: Only set the "last checked"/"lastTimeChecked" variable when data is retrieved, then update the "lastTimeChecked" to the current time to skip already processed data. However, this doesn't update or account for modifications and/or additions after the "last checked" time is updated. This is why the new feature for polling all events is added, to support updating previous records, etc, though costly (meant to be used along with the fixed "new time entry" trigger, except at a slower interval). 
> 
> \*\*Purpose\*\*: To put into place a system that gives a real time "feel" to clockify API updates while not requiring the use of webhooks and port forwarding. (this is useful for home servers)
> 
> Illustrations: 
> \*note: I use task and time entry interchangeably here\*
> \### Previous method 
> !\[image\](https://github.com/user-attachments/assets/643d2eee-9053-4869-8dba-1fb73739a471)
> 
> \### New method
> !\[image\](https://github.com/user-attachments/assets/72cc45fc-c3bb-4452-825d-5e657ec74f63)
> 
> \### Update/manual insert workaround
> !\[image\](https://github.com/user-attachments/assets/70eb6a63-4f19-4d28-8267-5add335da1ff)
> 
> 
> \## Related Linear tickets, Github issues, and Community forum posts
> 
> 
> \[Community post\](https://community.n8n.io/t/polling-not-working-or-am-i-doing-something-wrong/10576/2)
> 
> \## Review / Merge checklist
> 
> \- \[x\] PR title and summary are descriptive. (\[conventions\](../blob/master/.github/pull\_request\_title\_conventions.md)) 
> \- \[\] \[Docs updated\](https://github.com/n8n-io/n8n-docs) or follow-up ticket created. (In progress) 
> \- \[\] Tests included. (In progress)
> \- \[\] PR Labeled with \`release/backport\` (if the PR is an urgent fix that needs to be backported) N/A

---

<div class="post-metadata">

**Author:** ![Vinod\_Kanted](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/vinod_kanted/32/45875_2.png) [@Vinod\_Kanted](https://community.n8n.io/u/Vinod_Kanted)\
**Post date:** [December 20, 2024, 4:05am UTC](https://community.n8n.io/t/clockify-to-google-sheets/63695/3 "2024-12-20T04:05:07Z")

</div>

The GitHub post is pointing to something else, I cannot get any data from Clockify to Google Sheets. ideally, we should be able to get some data. please correct me if I am wrong

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\
**Post date:** [March 20, 2025, 4:05am UTC](https://community.n8n.io/t/clockify-to-google-sheets/63695/4 "2025-03-20T04:05:45Z")

</div>

Closed on March 20, 2025, 4:05am UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
