Google Calendar
Overview
Section titled “Overview”Phinite’s Google Calendar predefined tool lets workspace assistants call Google Calendar APIs through DevStudio after you save a connection under Integrations → Predefined tools.
Create, update, and query events, check availability, send invites,
What this integration enables
Section titled “What this integration enables”- Automate workflows using this predefined tool from agent graphs
- Connect once under Integrations and reuse across assistants
- Enable individual subtools per agent in Graph Studio
Required credentials
Section titled “Required credentials”- See integration configuration fields in Phinite
Setup steps
Section titled “Setup steps”- Create a Google Cloud project, enable Calendar API, and configure OAuth or a service account.
- Log into your Phinite workspace at app.phinite.ai
- Navigate to Integrations → Predefined tools
- Select Google Calendar
- Click + Add Configuration
- Enter the credential fields listed above
- Select assistants that should use this connection
- Click Save Configuration
Configure in Graph Studio
Section titled “Configure in Graph Studio”- Open an agent in Graph Studio
- Select the agent node → Tools tab → Add a new tool
- Choose GoogleCalendarTool (or search for Google Calendar)
- Select your saved connection or add a new one
- Enable the subtools your workflow needs and save
Predefined tools
Section titled “Predefined tools”Phinite provides 7 subtools for Google Calendar:
- List Events: List upcoming events from a calendar
- Create Event: Create a new calendar event
- Update Event: Update an existing calendar event
- Delete Event: Delete a calendar event
- Fetch All Events: Fetch events within a date range
- Find Available Slots: Find available time slots between dates
- List Calendars: List calendars for the authenticated user
Documentation & resources
Section titled “Documentation & resources”- Official documentation:
https://developers.google.com/calendar - Phinite documentation: Google Calendar
- Store API keys and tokens securely; many providers show secrets only once
- Use separate connections for Dev, UAT, and Prod environments where possible
- Test with a minimal subtool call after saving credentials

