@zapier/google-calendar-connector
v0.2.18
Published
Agent-callable Google Calendar tools — create, update, move, search, and delete events, manage calendars, check free/busy availability, resolve event colors, and manage calendar sharing. Use when the user mentions Google Calendar or wants to schedule, fin
Maintainers
Readme
@zapier/google-calendar-connector
Agent-callable Google Calendar tools. Create, read, update, move, and delete events; search a calendar; list and create calendars; check free/busy availability; resolve the event-color palette; and manage calendar sharing (ACL) — all over the Google Calendar API v3. Authentication is OAuth 2.0 over a single connection; capability is gated by scope and by each calendar's access role, not by token type. Use it when an agent needs to schedule, find, reschedule, or share calendar events and availability.
Independent, unofficial connector for Google Calendar. Not affiliated with, endorsed by, or sponsored by Google Calendar. "Google Calendar" is a trademark of its owner, used only to identify the service this connector works with.
When to use this
- Scheduling, finding, rescheduling, moving, or cancelling Google Calendar events from an agent.
- Checking when someone is busy or free across one or more calendars before proposing a time.
- Listing or creating calendars, reading a calendar's timezone, or managing who a calendar is shared with.
When NOT to use this
- Real-time event triggers / push notifications (new-event, event-updated) — this connector is request/response only; use a Zapier trigger or the Calendar watch API.
- Renaming or deleting calendars, clearing all events at once, or importing externally-originated events — these are intentionally out of scope.
- Gmail, Google Drive, or other Google products — use their dedicated connectors.
Install
This connector is the same artifact across four shapes: MCP server, CLI bin, importable Node module, and an Agent Skill anchored by SKILL.md. Pick the shape that matches how your agent runs.
# Run a script with zero install — npx fetches the package on first use
export <ENV_VAR>=xxx
npx @zapier/google-calendar-connector@latest run <script> '<input-json>' --connection env:<ENV_VAR>
# Install as a dependency to import the functions in your own code
npm install @zapier/google-calendar-connector
# Or install as an Agent Skill (https://agentskills.io)
npx skills add zapier/connectors --skill google-calendarAuth is one [<resolver>:]<value> connection string passed with --connection — a selector, not the secret. The <resolver>: prefix is optional; a bare value is claimed by the first matching resolver. See Auth below for the with/without-Zapier tradeoffs and how to find a connection ID.
MCP server
Run the connector as an MCP server over stdio so any MCP-aware client (Claude Desktop, Cursor, Claude Code, …) auto-discovers the scripts as tools — add one stanza to the client's config:
// e.g. claude_desktop_config.json or .cursor/mcp.json
{
"mcpServers": {
"google-calendar": {
"command": "npx",
"args": ["@zapier/google-calendar-connector", "mcp"]
}
}
}--connection is optional — omit it to pass a connection per tool call, or add "--connection", "zapier:<connection-id>" (or "env:<ENV_VAR>" with "env": { "<ENV_VAR>": "xxx" }) to args to set a default.
Cloning the source
You don't need to clone anything to use this connector — the options above already cover that. Want the actual repo source instead, to read the script code, browse references/, run this connector's tests, or hack on it? Clone with a path filter so you only fetch this one connector, not the whole catalog:
git clone --filter=blob:none --sparse https://github.com/zapier/connectors.git
cd connectors && git sparse-checkout set apps/google-calendar
cd apps/google-calendar && npm installSee the main README to clone several connectors at once.
Scripts
| Script | Description |
| -------------------- | --------------------------------------------------------------------------------------------- |
| createEvent | Create an event (timed/all-day, recurring, attendees, reminders, color, Google Meet). |
| quickAddEvent | Create an event from a natural-language phrase (lossy — title + time only). |
| updateEvent | Partially update an event (array fields replace; use addEventAttendees to add guests). |
| addEventAttendees | Add guests to an event without removing the existing attendees. |
| moveEvent | Move an event to another calendar (default events only). |
| deleteEvent | Delete an event (idempotent — already-deleted events still succeed). |
| listEvents | List/search events on a calendar by time window, text, or event type. |
| getEvent | Retrieve a single event by id (e.g. to read a resolved Google Meet link). |
| listEventInstances | List the occurrences of a recurring event; resolves instance ids for single-occurrence edits. |
| listCalendars | List calendars with id, access role, primary flag, and timezone. |
| getCalendar | Get a calendar's metadata; getCalendar("primary") returns the user's default timezone. |
| createCalendar | Create a new secondary calendar. |
| queryFreeBusy | Return busy time blocks across one or more calendars in a window. |
| getColors | Return the event + calendar color palettes (colorId index → hex). |
| listAclRules | List a calendar's sharing rules (requires the owner role). |
| createAclRule | Share a calendar with a user/group/domain at a role (requires owner). |
| deleteAclRule | Remove a sharing rule / revoke access (requires owner). |
Run npx @zapier/google-calendar-connector@latest run <script> --help to see any script's exact input contract + the available resolvers.
Usage
Each named export is the consumer-facing (input, opts) => Promise<{ data, meta }> function. Pass auth as one [<resolver>:]<value> string, e.g. { connection: "env:<ENV_VAR>" }.
import { createEvent } from "@zapier/google-calendar-connector";
// Each named export is the consumer-facing (input, opts) => Promise<{ data, meta }>.
const { data, meta } = await createEvent(
{
calendarId: "primary",
summary: "Sync with Sam",
start: {
dateTime: "2026-06-18T15:00:00-07:00",
timeZone: "America/Los_Angeles",
},
end: {
dateTime: "2026-06-18T15:30:00-07:00",
timeZone: "America/Los_Angeles",
},
},
{ connection: "env:<ENV_VAR>" },
);
// data is the created Event (id, htmlLink, start, end, …); meta.outputDataValidation reports
// what validation did. Pass { skipOutputDataValidation: true } to receive the raw API output.Auth
Already have a connection value? Pass it as shown above — --connection for the CLI/MCP shapes, { connection } for imported functions. No connection yet? Pick one:
| | Load |
| ------------------------------------ | ---------------------------------------------------------------------- |
| Pass the credential directly | references/use-without-zapier.md |
| Route it through a Zapier connection | references/use-with-zapier.md |
Links
- Google Calendar API v3 reference — vendor API docs
Legal
Scope of license. Zapier licenses only the connector code in this package. Zapier grants no rights in Google Calendar's API, services, data, schemas, documentation, or other materials, which remain the property of Google Calendar. Your use of Google Calendar's API is governed by your own agreement with Google Calendar.
Trademarks and affiliation. Google Calendar and its logos are trademarks of their owner, used here only to identify the service this connector works with. This connector is not affiliated with, endorsed by, or sponsored by Google Calendar.
Your responsibility. This connector calls Google Calendar's API using credentials you supply. You are responsible for holding a valid Google Calendar account, for complying with Google Calendar's API terms, developer policies, and acceptable use rules, and for the data you send and receive through it.
No warranty. This connector is provided "as is," without warranty of any kind, and is not an official Google Calendar product. Zapier is not responsible for changes Google Calendar makes to its API or for any consequence of your use of Google Calendar's API. See the repository LICENSE for the full disclaimer.
Forks. You may fork and modify this connector under the Elastic License 2.0. You may state that your fork is "based on" Zapier's connector, but you may not use the "Zapier" name or logo as the name or branding of your fork, or in any way that suggests Zapier produces, endorses, or supports it.
Licensed under the Elastic License 2.0. See the repository LICENSE and NOTICE.
