Fix: Granola calendar not syncing or showing events
Your day is full and Granola's "Coming up" panel is empty. Or it shows three of your seven meetings, or shows them at the wrong hour, or showed them fine last week and stopped. Then the 10am call happens and no notification appears, so no note opens, so nothing gets transcribed, and you find out about all of this an hour after the meeting ended.
That last part is what makes calendar sync worth ten minutes of your attention rather than none. In Granola, the calendar is not a convenience panel. It is the trigger.
TL;DR
- Granola reads only the calendar of the account you signed in with, and only Google or Microsoft 365. Apple Calendar is not supported.
- Sharing a calendar to your Granola email is not enough. The events have to actually appear in your sign-in provider's calendar.
- Read-only calendar access needs approval in most Microsoft 365 orgs, and Granola is not yet in the Entra App Gallery, so an admin has to act.
- Signing out and back in is the fix for most cases, because it re-triggers the permission prompt.
- Some events never appear by design: declined events, Out of Office, Focus Time, and Working Location blocks.
Why an empty calendar means an empty transcript
Granola's notification docs spell out the chain. A notification fires one minute before a calendar event. Clicking it opens the video call URL, opens the note, and starts transcribing. No calendar event means no notification, no note, and no transcription.
There is a second detail in those docs that catches people: "Calendar notifications only appear for events with 2 or more attendees." A call you put on your own calendar as a placeholder, or a recurring block you use to hold time, will not prompt you even when the calendar is syncing perfectly.
There is a fallback. Granola watches for your microphone going live and prompts with "Huddle detected", "Call detected", or "Meeting detected" depending on the app, which catches Slack huddles and FaceTime calls. You still have to click the prompt. So a broken calendar shows up as the problem in Granola didn't record my meeting, one meeting at a time, and you go hunting for a recording bug when what broke was authorization.
What Granola's own docs say
The calendar sync troubleshooting page is unusually direct about the limits, and reading it saves an afternoon.
Granola pulls from the calendar of the email you sign in with, and nowhere else. If you signed in with Microsoft and your team's calendar lives in Google, sharing it to your address does nothing on its own. Per the docs, "sharing to your email address alone isn't enough". You have to add the calendar to your Outlook or Google calendar "so the events actually appear there". Then the sharing permission has to be full detail, because "Granola won't be able to see events if it's only able to see free/busy times".
Three hard stops. On-premises Exchange servers are not supported, only cloud Microsoft 365. Outlook public folder calendars are not supported at all, "even if your organization uses cloud-based Microsoft 365." And Apple Calendar is not supported, which is the one that surprises Mac users who assumed a Mac app would read the Mac calendar.
The Microsoft consent path is its own category of stuck. Granola's sign-in with Microsoft page lists the scopes it asks for, all read-only: User.Read, Calendars.Read, and Calendars.Read.Shared. In a locked-down tenant that produces an "Approval required" screen. Sometimes there is not even a "Request approval" button, which means your admin has to first turn on admin consent requests in Entra before you can ask for anything. The page closes with a line worth knowing before you file a ticket: "We are in the process of adding Granola to the 'Microsoft Entra App Gallery'. Until then, please use one of the above methods."
Google Workspace has a matching version. If your connection drops repeatedly after you reconnect it, the docs point at Workspace security policy revoking access, fixed by an admin allowlisting Granola under Security > Access and data control > API controls.
Worth ruling out an outage before any of this. Granola's status history logs auth incidents separately, including a July 16, 2026 outage where a third-party login provider went down and blocked new sign-ins for two and a half hours. If your fix is "sign out and sign back in", you want to know that signing back in is currently possible.
Fix it in Granola first
- Confirm the events exist in the right account. Open Google Calendar or Outlook on the web, signed in as the exact address you use for Granola. If the meetings are not there, nothing downstream will help.
- Check which calendars are toggled on. Click the cog next to "Coming up", or go to workspace name > Settings > Calendar. Secondary and team calendars are off until you turn them on.
- Sign out and sign back in. Workspace name in the bottom left > Settings > Sign out, then sign in with the same account and accept the calendar prompt. This is the documented fix for missing permissions, and it is the one that resolves most cases.
- Wait a few minutes. Sync is not instant. New and edited events take a couple of minutes to land.
- Fix the share properly if the calendar belongs to another account. Add it to your sign-in provider's calendar rather than just sharing it to your address, and grant "See all event details" instead of free/busy.
- Get admin consent if you are on Microsoft 365. Send your admin the Entra steps from Granola's docs. If they cannot enable consent requests, an admin signing in to Granola once and ticking "Consent on behalf of your organisation" clears it for everyone.
- Drop the VPN and check the network. Granola names VPNs and corporate network tooling as a cause, and publishes a domain allowlist guide for your IT team.
- Check the time zone in your calendar, not in Granola. Granola displays whatever time the source calendar stores. Wrong times in Granola almost always mean wrong times upstream.
Stay or switch
| Job | Stay with Granola | Switch to LUCI |
|---|---|---|
| Your calendar is Google or Microsoft 365 and sync works | Yes | Either works |
| You live in Apple Calendar | No, unsupported | Yes, no calendar connection required |
| Your org runs on-premises Exchange or public folder calendars | No, unsupported | Yes |
| Your IT team will not grant a third-party app calendar read access | No | Yes, nothing to authorize |
| You want capture that does not depend on an event being detected first | No | Yes, on-device |
What to do next
Two honest notes first. Most Granola calendar problems really are fixable in five minutes, usually at step 3, and the docs above are good ones. And the calendar connection buys real things, including meeting titles, attendee context, and pre-meeting briefs. Granola wants it for a reason.
The structural point stands anyway. Granola knows a meeting is happening because a third party told it, and that channel breaks in a lot of places: a provider it does not support, a scope your admin has not approved, a share that looks correct and is not. LUCI captures meetings on-device without needing calendar access to know a call is happening, so an unapproved app registration in Entra is not standing between you and your own notes. What gets captured joins the rest of your day instead of sitting in a per-meeting file, so "what did we agree in the Tuesday call?" resolves against your memory rather than a folder.
Side by side in LUCI vs Granola, the shortlist in Granola alternatives, or read whether Granola is actually local before you decide what it should be reading.
Frequently asked questions
Does Granola support Apple Calendar or iCloud?
No. Granola's documentation states plainly that it supports Google and Microsoft/Outlook calendars only, and does not currently support Apple Calendar. The workaround is to get those events into a Google or Microsoft calendar that the account you sign in to Granola with can see, either by subscribing to the iCloud calendar from Google Calendar or Outlook, or by moving the invites. Sharing the calendar to your Granola email address is not sufficient on its own, because Granola reads your sign-in provider's calendar rather than your inbox.
Why do some of my meetings show up in Granola and others don't?
Three usual causes. The calendar the event lives on may not be toggled on in Settings > Calendar, since only your primary calendar syncs by default. The event may be one of the types Granola deliberately hides: declined events, Out of Office, Focus Time, and Working Location blocks never appear. Or it may be a single-attendee event, which will show in "Coming up" but will not trigger the one-minute-before notification, because notifications only fire for events with two or more attendees.
My IT admin blocked Granola's calendar permissions. What are my options?
Granola requests read-only Microsoft scopes, User.Read, Calendars.Read, and Calendars.Read.Shared, and in many tenants that still needs admin consent. Your admin approves it in the Entra admin center under Enterprise apps > Admin consent requests, or by signing in to Granola themselves and consenting on behalf of the organization. Granola is not yet listed in the Entra App Gallery, so there is no pre-approved entry to enable. If your security team will not approve third-party calendar reads at all, a tool that does not ask for calendar access is the shorter path.
Granola showed my calendar before and suddenly stopped. What changed?
Usually a token or a policy rather than anything you did. Signing out and back in re-triggers the permission prompt and fixes most cases. If the connection drops again within days, the likely cause is a Google Workspace or Microsoft policy revoking third-party app access, which an admin resolves by allowlisting Granola in the Workspace Admin Console under Security > Access and data control > API controls. Rule out a service incident on Granola's status page first, since a login-provider outage looks identical from the outside.
