Choose Google, Outlook, or iCal
By Tristan Doehl · · Updated
Teetrack supports Google Calendar, Outlook, and calendar feeds in iCal format. The best starting point is the system where your work is already scheduled. The connection method affects authorisation and feed handling, while the review of imported work follows the same basic process.
Use Google or Outlook for a supported account
Google and Outlook connections use an authorisation flow with the provider. You sign in there and grant the requested access, then Teetrack can retrieve events without asking you to paste a calendar feed URL. The calendar integration reads events; it does not edit the source calendar.
Outlook supports personal Microsoft accounts as well as Microsoft 365 and Exchange Online. If your organisation requires administrator consent, ask its administrator to approve the connection before completing setup.
Use iCal when your calendar supplies a feed
An iCal connection uses a URL that returns calendar data. This is useful for providers that publish a compatible feed, including calendars without a direct Teetrack account connection. Teetrack must be able to fetch the URL, so an interactive login page is not a usable feed address. The URL must also use HTTPS; a webcal:// link is accepted and fetched over HTTPS.
Teetrack’s iCal parser does not expand recurrence rules (RRULE). A weekly meeting defined only by a recurrence rule will therefore show at most its first occurrence. Because Teetrack reads events from the last 30 days and the next 14, a series that began more than 30 days ago does not appear at all. Use a feed containing each occurrence as a separate event, or a Google or Outlook connection for the recurring schedule.
Feeds are limited to 1 MiB (1,048,576 bytes), and private or internal network addresses are rejected. Events without a time zone are read as UTC. Keep a private feed URL confidential because it can grant access to the event data, and use an updating feed rather than a one-time export.
Expect scheduled events, not finished records
Every connection type syncs on the same schedule: automatically every 30 minutes, with a manual refresh available after a five-minute cooldown. A change in the calendar therefore reaches Teetrack with some delay, whichever provider you choose. A synced event also records only what was planned, so a meeting that ended early looks the same as one that ran to schedule. That is why imported events become drafts to check rather than finished time records.
Compare the plan requirements
The Free plan supports one Google or Outlook connection for basic calendar viewing. Business supports up to ten connections and adds automatic draft import and iCal feeds. Pro removes the connection limit and adds calendar keyword matching.
A connection is a provider account or feed; an account can contain several calendars. None of the providers has a calendar picker in Teetrack’s current interface. Selecting particular calendars is only possible through the API and requires Business or higher, so do not look for that control during browser setup. An iCal feed is always a single calendar.
Test the connection with a familiar event
Follow the Google, Outlook, or iCal guide, then check an event whose date and duration you know. With iCal, choose the next occurrence of a recurring meeting, because that shows whether the feed lists occurrences the parser can read. Once the event appears correctly, the calendar import walkthrough explains which events become drafts and how to confirm them.
