Connect Google Calendar to Zed
Give Zed governed access to Google Calendar’s 13 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Google Calendar to Zed in four steps
Admins approve the server once. Everyone in Zed then gets it through the same governed connection.
- 1
Approve Google Calendar in Runlayer
Add Google Calendar from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Zed to Runlayer
Users add the Runlayer Plugin to Zed by following Runlayer’s setup guide. Zed reaches Google Calendar’s 13 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Zed setup guide - 3
Sign in to Google Calendar
Sign in the way Google Calendar requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Google Calendar from Zed
Google Calendar’s approved tools appear in Zed. Every call is checked against policy and recorded.
Tools
13 Google Calendar tools in Zed
Runlayer policy decides which of these Zed users can call. 4 read data only and 2 can change or delete data.
Create Calendar
Create a new calendar.
Create event
Create a new event in your Google Calendar with detailed options including attendees, location, reminders, and recurrence rules.
Delete Calendar
Delete a secondary calendar.
Delete event
Delete an event from your calendar.
Get event
Get detailed information about a specific calendar event including title, description, time, location, attendees, and recurrence rules.
Get free busy
Check free/busy information for calendars within a time range.
List calendars
List all calendars accessible to the authenticated user.
List events
List events from your Google Calendar.
Control
What Runlayer can see and stop in Zed
Some controls apply to every client at the gateway. Others depend on what Zed exposes to Runlayer.
Gateway policy (available)
Every Google Calendar call from Zed passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Zed as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Zed yet, so control happens at the gateway.
Frequently asked questions
Connect more