Google Calendar
productivity
Connect your personal Google Calendar so Ruby can see your schedule, find meetings, and check your availability.
Ask Ruby
6 read tools
Ruby reads from Google Calendar and grounds her answers in your data. Every connection starts read-only: she surfaces, summarizes, and drafts, and your team takes the action.
Get current date time
Get the current date and time (optionally in a specific timezone). Call this FIRST whenever the user asks about relative dates ('today', 'tomorrow', 'next Monday', 'this week') so you compute the right window before listing or searching events.
List calendars
List the calendars in the connected Google Calendar account (primary plus any secondary/shared calendars) with their ids and access roles. Use it to discover the calendar_id to pass to the event tools; calendar display names are NOT valid ids.
Events list
List events on a calendar within a time window. Use it to answer 'what's on my calendar', 'what meetings do I have', and to build a schedule view. Pass calendar_id (defaults to 'primary'), and an RFC3339 time_min/time_max window WITH a timezone offset (e.g. '2026-01-19T00:00:00-06:00'); call GOOGLECALENDAR_GET_CURRENT_DATE_TIME first for relative dates. Set single_events:true and order_by:'startTime' for a clean chronological list.
Find event
Search for events by free-text query and/or a time window. Use it to find a specific meeting ('find my meeting with the adjuster', 'when is the inspection'). Read one event in full with GOOGLECALENDAR_EVENTS_GET using its id.
Events get
Read one event in full by its event_id (from GOOGLECALENDAR_EVENTS_LIST or GOOGLECALENDAR_FIND_EVENT): summary, start/end, location, description, attendees, and conferencing.
Find free slots
Find free and busy time blocks across one or more calendars within a window. Use it for availability and scheduling questions ('when am I free this week', 'do I have time Tuesday afternoon'). Returns busy intervals and the computed free gaps; no event titles (use the event tools for those).
2 write tools, off by default
Let Ruby put things on the calendar and move them, not just read it. Attendees are invited and notified when it does.
An admin switches a connection to read-write in Settings > Integrations. From then on every write waits for a human’s approval before it leaves, by default, and every one lands in your audit log with what changed.
Create event
Create an event on the connected calendar. Attendees are invited and notified, so confirm the time, timezone, and guest list first. Use GOOGLECALENDAR_FIND_FREE_SLOTS to pick a time that works.
Patch event
Change fields on an existing calendar event (time, title, location, attendees). Get `event_id` from GOOGLECALENDAR_FIND_EVENT; it is an opaque id, not the title. Passing `attendees` REPLACES the whole guest list.
Built for restoration, not bolted on.
Grounded answers
Ruby reads Google Calendar live and cites what she found, so answers reflect your actual data, not a stale export.
Reads by default
Every connection starts read-only. Ruby surfaces and drafts while your team takes the action; writes are opt-in per connection, human-approved by default, and always logged.
Managed, secure auth
Connect with one click. Tokens are encrypted and scoped per company; revoke access any time.
Knows restoration
Ruby understands jobs, claims, drying logs, and AR, so Google Calendar data lands in the right operational context.
Connect once, then just ask.
Connect Google Calendar once in Ruby. Ask in the Ruby app, or bring the same secure connection into the assistant your team already uses.
Ruby
Ask in the Ruby app and get an answer grounded in Google Calendar and the rest of your connected stack.
Claude
Bring the same secure Google Calendar connection into Claude so it can answer with your live data.
ChatGPT
Use Google Calendar from ChatGPT with the same per-company, permissioned access Ruby uses.
Frequently asked questions
Do I need developer credentials to connect Google Calendar?
No. Google Calendar connects with a single click, Ruby handles the OAuth handshake and token refresh for you.
Can Ruby change anything in Google Calendar?
Not unless you turn it on. Every Google Calendar connection starts read-only. An admin can switch a connection to read-write in Settings > Integrations; from then on each write Ruby makes waits for a human's approval before it leaves (by default; the same admin can switch that off) and is recorded in your audit log either way.
Is my Google Calendar data secure?
Credentials are encrypted at rest and access is scoped per company. You can revoke the connection at any time from Settings > Integrations, which immediately cuts Ruby off.
Can I use Google Calendar alongside my other tools?
Yes. Ruby reasons across every tool you connect at once, so she can tie Google Calendar to your CRM, accounting, email, and documentation in a single answer.
