Recipe Batch Invite To Event
Batch-add attendee emails to an existing Google Calendar event and trigger update notifications without editing the event in the UI.
Overview
Recipe Batch Invite To Event is an agent skill for the Grow phase that adds a list of attendees to an existing Google Calendar event via gws CLI and sends update notifications.
Install
npx skills add https://github.com/googleworkspace/cli --skill recipe-batch-invite-to-eventWhat is this skill?
- 3-step recipe: get event, patch attendees with sendUpdates=all, verify with a second get
- Patches multiple attendees in one JSON payload (example shows three emails)
- Depends on gws-calendar and the gws CLI binary
- Uses calendarId primary plus explicit eventId placeholders
- OpenClaw recipe metadata: scheduling domain, version 0.22.5
- example attendee list of 3 emails
Adoption & trust: 15.5k installs on skills.sh; 26.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You already scheduled a Google Calendar event but still need to add several attendee emails and notify them without manual UI edits.
Who is it for?
Solo builders automating invite lists for demos, onboarding sessions, or recurring meetings when eventId and calendar access are already set up.
Skip if: Creating new events from scratch, managing RSVPs at scale without Google Workspace auth, or teams that cannot run the gws binary or load gws-calendar.
When should I use this skill?
Add a list of attendees to an existing Google Calendar event and send notifications.
What do I get? / Deliverables
The event’s attendees array is updated in one patch, notifications go out when sendUpdates is set to all, and a follow-up get confirms the final guest list.
- Updated Calendar event with expanded attendees array
- Optional verification output from events get
Recommended Skills
Journey fit
Canonical shelf is Grow because solo builders use this after they have users or partners to invite—to demos, onboarding calls, or community sessions—rather than when first wiring Calendar APIs. Lifecycle fits coordinated touchpoints (webinars, customer calls, cohort kickoffs) where one event ID already exists and the attendee list still changes.
How it compares
Use this recipe for a known eventId patch workflow instead of ad-hoc Calendar UI clicks or a one-off chat script that skips sendUpdates verification.
Common Questions / FAQ
Who is recipe-batch-invite-to-event for?
Indie builders and small teams using Claude Code, Cursor, or similar agents to maintain Google Calendar guest lists through the gws CLI after gws-calendar is loaded.
When should I use recipe-batch-invite-to-event?
Use it in Grow lifecycle work when you need to add alice@, bob@, and carol@ (or any batch) to an existing primary-calendar event and confirm attendees via get—typically after launch distribution sets the meeting time.
Is recipe-batch-invite-to-event safe to install?
It only documents Calendar API patch commands; review the Security Audits panel on this Prism page and your Google OAuth scopes before granting an agent calendar write access.
Workflow Chain
Requires first: gws calendar
SKILL.md
READMESKILL.md - Recipe Batch Invite To Event
# Add Multiple Attendees to a Calendar Event > **PREREQUISITE:** Load the following skills to execute this recipe: `gws-calendar` Add a list of attendees to an existing Google Calendar event and send notifications. ## Steps 1. Get the event: `gws calendar events get --params '{"calendarId": "primary", "eventId": "EVENT_ID"}'` 2. Add attendees: `gws calendar events patch --params '{"calendarId": "primary", "eventId": "EVENT_ID", "sendUpdates": "all"}' --json '{"attendees": [{"email": "alice@company.com"}, {"email": "bob@company.com"}, {"email": "carol@company.com"}]}'` 3. Verify attendees: `gws calendar events get --params '{"calendarId": "primary", "eventId": "EVENT_ID"}'`