Skip to content

Microsoft / Outlook Calendar

The Microsoft Calendar integration imports events from your primary Outlook calendar into Track as time entries. Works for personal Microsoft accounts and Microsoft 365 (work / school) accounts alike, subject to your tenant’s policy.

Like the Google Calendar integration, this is per user — each teammate connects their own account.

  1. Open SettingsIntegrations in Track.
  2. Click Connect next to Microsoft Calendar.
  3. Sign in at the Microsoft prompt.
  4. Grant Track read-only access.
  5. You’ll land back in Looped with the integration showing Connected.

Track stores tokens server-side and refreshes them automatically. To revoke, click Disconnect in Looped, or revoke from account.microsoft.comPrivacyApp access.

The time-logger gets an Import from Calendar button once you’re connected:

  1. Pick a date range.
  2. Track lists events in that range you haven’t already imported.
  3. Tick the events you want. Edit task name or assign a project before confirming.
  4. Import.

Each ticked event becomes a time entry — title becomes task name, length becomes the hours, the start time becomes the date.

  • All-day events — no length to convert
  • Declined invites — only events you’ve accepted appear
  • Calendars other than your primary — only the primary calendar is read today

Track records (connection, providerEventId) for every imported event, so re-running the import on the same range doesn’t double up. Deleting an imported time entry also removes the dedup record, so you can re-import the event later if you change your mind.

Track requests read-only scope (Calendars.Read). It cannot create, edit, or delete events.

If your organization uses Microsoft 365 with strict tenant policies, your IT admin may need to permit Looped explicitly before the OAuth consent screen will work. Symptoms:

  • The consent screen says “Need admin approval”.
  • Sign-in completes but no events ever load.

In both cases, ask your admin to grant tenant-wide delegated consent for the Looped app from the Microsoft Entra admin center.

If your admin uses a direct admin-consent URL, it should use your tenant ID or organizations, not common:

https://login.microsoftonline.com/{tenant}/v2.0/adminconsent?client_id={client_id}&scope=https://graph.microsoft.com/User.Read%20https://graph.microsoft.com/Calendars.Read%20offline_access&redirect_uri={redirect_uri}

After consent is granted, each teammate still connects their own Microsoft account in Track, but non-admin users should not be asked to request permission again for the granted scopes.

  • “Authorization expired” — refresh token rotated. Disconnect and reconnect.
  • No events show up — confirm date range is right; confirm the connected account actually has events (it might be the wrong Microsoft account if you have multiple).
  • Sign-in error mentioning the tenant — see Enterprise tenants above.