What Runner can do with Google Calendar. These are grounded in the real backend connector definitions, not generic marketing filler.
Find the right meeting window
gcal_find_available_slotsFind available meeting slots across multiple attendees using free/busy data.
“Find 3 openings next week for a 30-minute founder follow-up with Maya and Oliver.”
Runner proposes real slots instead of making you manually compare calendars.
Look up the event you are about to walk into
gcal_find_eventsRobust event lookup for next, previous, date-range, or text-based event queries.
“Show me today's investor meetings and the exact titles and times.”
The meeting schedule becomes part of the operating context before you respond or prepare.
Create the follow-up meeting
gcal_create_eventCreate a calendar event with optional Google Meet link, recurrence, and idempotency protection.
“Create a 45-minute follow-up next Thursday afternoon with a Meet link and add the thread participants.”
The next step turns into a real calendar commitment instead of a vague intention.
Adjust or RSVP without leaving the workflow
gcal_update_eventUpdate an event, including attendees, timing, recurrence, and Meet links.
“Move tomorrow's board prep to 2 PM and add the finance lead.”
Runner keeps the event current while you stay in the same working surface.
Accept, decline, or go tentative
gcal_rsvp_eventRespond to a calendar invitation with accept, decline, or tentative.
“Mark the partner sync as tentative until I confirm the travel window.”
Calendar state stays accurate without interrupting the rest of the workflow.