Sistava

Why Your AI Cannot See Your Calendar, and How to Fix It

How-to — — by Mahmoud Zalt

Every real reason an AI assistant cannot read your calendar, from plan limits and admin blocks to expired sign-ins, plus a five minute diagnostic.

You connected your calendar. The setting says connected. And the assistant still tells you it has no access, or worse, confidently describes a week that is not yours. It is a maddening failure because everything looks correct from where you are standing.

The reason it looks correct is that calendar access has four separate gates, and each one can be shut independently: your plan, your administrator, the account you picked, and the permissions you granted. A green toggle only proves the first gate opened.

Below is every cause worth checking, in the order that finds the problem fastest, with the fix for each. Start by working out which of the three shapes your failure has.

First, which failure is it?

There are only three symptoms, and they point at completely different gates. Name yours before you touch a setting, because the fix for a blocked connection will not help a connection that is working on the wrong account.

SymptomLikely gateWhere to look first
There is no calendar connector to turn onPlan or administratorYour plan's feature list, then your organisation's connector settings
The connection fails or loops during sign-inAdministrator, on a managed accountGoogle Workspace or Microsoft admin controls
It says connected but finds no eventsWrong account, or calendar not sharedWhich account you approved, and who owns the calendar
It found some events but missed othersSecondary calendarsTest an event that lives on a non-default calendar
It worked for weeks, then stoppedExpired or revoked sign-inYour Google Account's third party access list
It reads fine but refuses to bookWrite permissionThe permissions you approved on the consent screen

It never connected: plan and administrator gates

If the connector is missing from your settings entirely rather than switched off, this is not a bug. Calendar connectors are a paid or gated feature almost everywhere. Anthropic's documentation lists the Google Calendar integration as available on Pro, Max, Team and Enterprise plans, and their Microsoft 365 connector as available on all plans but gated at the tenant.

On a team account there is a second gate above you. Anthropic states that on Team and Enterprise plans an Owner or Primary Owner must enable connectors for the organisation before individual users can authenticate, and that for Microsoft 365 a Microsoft Entra Global Administrator has to authorise the integration before anyone in the tenant can connect at all.

The third gate is on the calendar side, and it is the one that produces a sign-in that just fails. Google Workspace administrators control third party app access under Security, then Access and data control, then API controls. Apps without an access policy are blocked by default, and a user's attempt lands on a review list in the admin console where it can be allowed, dismissed or blocked.

What to ask your administrator

  1. Name the exact app — Say which assistant you are connecting and that its access request should be waiting in the admin console review list. Vague requests get parked.
  2. Ask for a trusted or limited policy — Google's app access control lets an admin mark an app trusted, limited to specific scopes, or blocked. Limited to calendar scopes is a reasonable ask and easier to approve than full trust.
  3. For Microsoft, ask for tenant consent — A Microsoft Entra Global Administrator has to grant a one-time consent. Nobody in the tenant can connect until that happens, no matter what their own plan says.
  4. Ask about write permissions separately — Reading and writing are different grants. Anthropic notes organisations that connected before write tools existed have them blocked by default until an admin re-consents to the updated scopes.

One more thing worth knowing before you blame the assistant: connectors are also surface specific. Developers have reported a connector working in a desktop app while the same account fails in a command line tool with a permission scope error, so if one surface works and another does not, the account is probably fine.

It connected but sees nothing

This is the most common shape, and the most common cause is embarrassingly simple. You were signed into more than one Google or Microsoft account, and the approval screen used the wrong one. The connector is working perfectly, it is just reading somebody else's empty calendar.

Second cause: the events are not on a calendar that account can see. Anthropic states plainly that only calendars you have access to can be searched, and that the connector mirrors your existing calendar permissions. If a client's calendar was never shared with the connected address, it does not exist as far as the assistant is concerned.

Third cause, and this one is a genuine reported defect rather than a setting. Users on OpenAI's developer forum have reported the Google Calendar connector searching only the primary calendar and ignoring secondary calendars, even with permission granted across all of them. If your work lives on a second calendar, test that specifically before assuming the whole connection is broken.

It worked for weeks, then went blind

A connection that used to work and now does not has almost always lost its sign-in rather than its settings. Google documents exactly when this happens, and none of the reasons produce a warning on your side.

The fix is the same for all six: disconnect properly on both sides, then reconnect. Turn the connector off in the assistant, then remove the app from your Google Account's third party access list, then connect again from scratch. Removing it on only one side is why reconnecting sometimes appears to do nothing.

It reads your calendar but refuses to change it

This is not a fault. Reading and writing are separate permissions, and several assistants ship read only by default. Anthropic's own documentation page for the Google Calendar integration warns that Claude cannot create, modify or delete events or send invitations, while their help centre describes a connector that can do all of those.

Both are accurate for different setups, which is exactly why guessing is pointless. Ask for a ten minute throwaway event tomorrow called test. If it appears, you have write access. If it does not, no rewording of the request will change the permission you were granted.

If what you actually wanted was a calendar that runs itself, that is a different category of tool. An AI Employee from Sistava holds the calendar connection as part of a job rather than a chat session, with standing rules you write once: protect these mornings, keep this much space between calls, ask me before touching a delivery day.

You do not have to connect anything to see how that feels either. Several of our free tools run in the browser with no account and no calendar access at all, which is a reasonable way to judge the quality of the work before you grant anything real.

The five minute diagnostic

Run these in order. Each step rules out a whole class of cause, so stopping early is normal and the whole thing rarely takes the full five minutes.

Find the closed gate

  1. Check the connector exists at all — If there is no calendar connector in your settings, stop. This is a plan or organisation question, not a configuration one, and no amount of reconnecting will create it.
  2. Confirm which account is connected — Find the connected address and read it carefully. If you hold two accounts with the same provider, assume you picked the wrong one until you have proved otherwise.
  3. Ask about one named real event — Something specific from this week. A correct answer proves reading works. A wrong or missing answer tells you the gate is further down.
  4. Test a secondary calendar — Ask about an event that does not live on your default calendar. This separates a broken connection from the reported habit of only searching the primary calendar.
  5. Test writing with a throwaway event — Ask for a ten minute event called test tomorrow. This tells you in seconds whether you hold read access or read and write.
  6. Disconnect on both sides, then reconnect — Only if the steps above point at an expired grant. Remove it in the assistant and in your account's third party access list, then connect again and read the permission list this time.

If all six pass and the assistant is still wrong about your week, the problem is usually staleness rather than access. A calendar you added by subscription URL is a slow copy, not a live view, and an assistant reading that copy will confidently report a schedule that was accurate yesterday.

What none of this fixes

Worth saying plainly, because it saves people from chasing a setting that does not exist. A working connection is not a working calendar assistant.

FAQ

Why does my assistant say it has no calendar access when the setting says connected?

Usually because the sign-in expired or you approved the connection with a different account than the one holding your events. Check the connected address first, then disconnect on both sides and reconnect. Google documents several ways an access grant stops working silently, including six months of disuse and a password change on a grant that includes mail scopes.

Why can it see some events but not others?

Two likely reasons. Connectors mirror the calendar permissions the connected account already has, so a calendar nobody shared with that address is invisible. Separately, users on OpenAI's developer forum have reported the Google Calendar connector searching only the primary calendar and skipping secondary ones.

Why is there no calendar connector in my settings at all?

Your plan does not include it, or an administrator has not enabled it. Anthropic lists its Google Calendar integration on Pro, Max, Team and Enterprise, and requires an Owner to enable connectors for a Team or Enterprise organisation. Connected apps in ChatGPT are likewise a paid plan feature, so on a plan without them the section is absent rather than greyed out.

The sign-in fails on my work account. What is happening?

Most likely your administrator's third party app policy. In Google Workspace, apps without an access policy are blocked by default under Security, then Access and data control, then API controls, and your attempt appears on a review list in the admin console. For Microsoft 365 connectors, a Microsoft Entra Global Administrator must grant a one-time tenant consent before anyone can connect.

It reads my calendar but will not book anything. Is that a bug?

No, it is a separate permission. Several assistants ship read only calendar access. Ask it to create a ten minute throwaway event tomorrow and see whether it appears. If it cannot, the grant you approved did not include writing, and only reconnecting with the wider permission will change that.

Why does it describe a week that is out of date?

Check whether the calendar it reads is a subscription rather than the original. A calendar added by URL is a read only copy, Google does not publish how often it refreshes, and the interface has no manual refresh, so the copy can lag by hours.

Sources