feat(google-calendar): add RSVP operation to respond to invitations

[waleedlatif1]

Summary

• Add a Respond to Invitation (RSVP) operation to the Google Calendar block (google_calendar_respond / _v2) — accept, decline, or tentative, with an optional note
• Reads the event, finds the attendee flagged self, then PATCHes with attendeesOmitted: true and only that entry, so just your response changes and every other guest is preserved
• Passing a recurring-event instance ID (what List Events returns) changes the response for that occurrence only; the series ID applies to every occurrence
• Verifies the response Google returns reflects the new status and fails loudly if it doesn't; errors clearly when the calendar isn't an attendee
• Previously the only write paths were Update Event / Invite Attendees, which replace the guest list and can't set your own responseStatus
• Adds an rsvp-to-event skill, regenerates tool metadata and integration docs

Type of Change

• New feature

Testing

• Unit tests for request shape, self-only patch body, occurrence targeting, validation, Google error surfacing, and result verification (confirmed they fail when attendeesOmitted is dropped)
• bun run lint, check:audits (47/47), block registry check, docs-manifest:check, type-check all pass

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Sep 19, 2026 7:21pm UTC

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; no actionable new defects or outstanding previous findings remain.

Summary

Adds an RSVP operation to the Google Calendar integration.

• Reads the event to identify the connected account’s attendee entry, then PATCHes only that attendee.
• Supports accepted, declined, and tentative responses, optional notes, notification preferences, recurring-event occurrence IDs, and cancellation propagation.
• Registers both legacy and API-aligned v2 tools and updates block configuration, generated metadata, deployment metadata, tests, and documentation.

Diagram

sequenceDiagram
  participant Workflow
  participant RSVPTool
  participant Google as Google Calendar API
  Workflow->>RSVPTool: Respond(eventId, status, optional note)
  RSVPTool->>Google: GET event
  Google-->>RSVPTool: Event and attendees
  RSVPTool->>RSVPTool: "Find attendee where self=true"
  RSVPTool->>Google: "PATCH self attendee only<br/>attendeesOmitted=true"
  Google-->>RSVPTool: Updated event
  RSVPTool->>RSVPTool: Verify status and requested note
  RSVPTool-->>Workflow: Confirmed RSVP result

Loading

_{Reviews (3) · Last reviewed commit: "fix(google-calendar): verify the RSVP no..."}

[cubic-dev-ai]

All reported issues were addressed across 11 files

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

All reported issues were addressed across 11 files

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 11 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}