Track your time on Google Calendar 📅 using Alfred.
Have you ever asked yourself the question, What did I do today?
.
If you did and could not answer, this Alfred workflow is for you.
Sometimes we have so many different tasks and interrupt that it is easy to lose track.
You can track them manually, but this approach is error-prone, time-consuming, and tedious.
This workflow lets you to leverage Alfred's power to track your work easily.
- Download the latest workflow from the releases page
- Add it to Alfred (double-click is usually enough)
- Run
tt authorize
&tt setup
- Track your time like a pro 😎
Command | Explanation |
---|---|
tt authorize | Authorize Alfred to access your Google Calendar. |
tt deauthorize | Revoke the access from your Google Calendar. |
tt setup | Create a Tracking calendar and store its ID in the configuration. |
tt start | Start tracking a new task. |
tt stop | Stop tracking an ongoing task and add it to Google Calendar. |
tt list | List the ongoing tasks. |
tt cancel | Cancel an ongoing task. |
tt track | Track a new task with already known duration. |
tt update | Check if there are updates available. |
Pro trick: you can omit the tt
prefix.
If you find any bugs or want to propose a new feature, please open an issue to discuss it.
On February. 2022, Google deprecated the use of Loopback IP addresses on the Chrome OAuth client type.
The change forced us to migrate to the Desktop OAuth client type.
Desktop clients require a client_secret
as part of the OAuth authorization flow, which we need to distribute together as part of the Alfred package.
Without appropriate protection, an attacker able to sniff HTTP requests on the machine might try to intercept the OAuth code
and exchange it for a valid access_token
.
This project prevents this and similar attacks by implementing the OAuth Proof Key for Code Exchange (PKCE) extension.
This repository contains free software released under the MIT Licence. Please check out the LICENSE file for details.