An AI scheduler that knows when you’re free.
Connect Google Calendar and your Oya AI employee can find available slots, propose meeting times to prospects, create events with the right invitees and notes, and reschedule when things shift. It works across multiple calendars and respects your time zone.
What it does
Find availability
Query free/busy across one or many calendars and propose times that actually work — including buffer rules, working-hours, and "no meetings before 10am" preferences in your prompt.
Create and update events
Book meetings with the right attendees, descriptions, locations, and reminders. Reschedule, cancel, or update an existing event by query (e.g. "the demo with Acme on Tuesday").
Time-zone-aware
Your agent handles the time-zone math — propose 3pm London and the invitee in New York sees their local time. Important for cross-timezone scheduling without 5 emails of confusion.
How to connect Google Calendar
- 1
Click Connect Google Calendar
On your AI employee’s Channels & Apps page, click Google Calendar and pick the Google account. Standard Google OAuth — your tokens stay encrypted in our store.
- 2
Approve calendar scopes
We request only the calendar scopes needed: read free/busy, list calendars, and create/update events. You see the exact list before approving.
- 3
Tell your agent which calendar(s) to use
In your agent’s system prompt, name the calendar(s) — "primary", a specific shared calendar, or rotate across team calendars. The agent passes that to every Calendar API call.
- 4
Wire scheduling routines (optional)
Combine with Gmail or Slack so your agent can read a meeting request, find a slot, send a confirmation email, and put it on the calendar — end to end, without you in the middle.
Detailed walkthrough with screenshots: Channels & Apps in the docs.
What it doesn’t do (yet)
We’d rather be upfront about the edges than promise things we don’t deliver.
- Smart re-scheduling across attendees still needs a human nudge — the agent proposes, you confirm before sending updates to invitees.
- Recurring event edits (modify-this-and-future occurrences) work but are best double-checked before the agent commits the change.
- Google Workspace calendar resource booking (rooms, equipment) is supported via Calendar API but needs the right Workspace permissions on your end.
Frequently asked
Can the agent see all of my calendars?
Only the calendars you’ve given the connected Google account access to, and only when a run reads them. The agent doesn’t have a background view of your week — every read is tied to a run.
How does it handle time zones?
Every Calendar API call is in UTC under the hood, then rendered in the calendar/invitee’s local time zone. If you live in multiple time zones, tell your agent that in the system prompt and it’ll narrate times in both.
Can my agent create events on a colleague’s calendar?
Yes if your connected account has write access to that calendar (e.g. shared team calendars). For colleagues’ private calendars you’d need the colleague to share with you first.
Will the agent send invites without my approval?
That’s up to your configuration. Most teams have the agent draft an event and ping a human for approval before sending invites — but for low-stakes or recurring patterns (e.g. "book a 15-min weekly check-in"), full autonomy works fine.
How do I disconnect?
From the agent’s Channels & Apps page, click Disconnect on the Google Calendar tile. Tokens are revoked immediately. Belt-and-braces: revoke from your Google Account → Security → Third-party apps.
Does Oya cache my calendar data?
No. We hit the Calendar API live for every read. The only persistence is the run history record of "agent looked up free/busy at this time and got these slots" — for your audit, not for caching.
A note on AI accuracy
Oya’s AI employees are powered by large language models and may produce inaccurate, incomplete, or out-of-date responses. They are tools to assist your work, not authoritative sources. Always verify important information — especially numbers, dates, names, and any business or financial action — before relying on AI-generated output. If your AI employee suggests a destructive action (deleting data, sending money, posting publicly), confirm it yourself before approving.
No model training
Your data is not used to train AI models. It’s used to do the work you asked for, then logged in your run history for your audit.
Full audit trail
Every AI employee action maps to a run in Oya. Inputs, outputs, tools used, cost — all visible and auditable.
Get your calendar back.
Connect Google Calendar in one click. $10 in free credits to start.