gws-calendar-insert

name	gws-calendar-insert
description	Google Calendar: Create a new event.
metadata	{"openclaw":{"category":"productivity","requires":{"bins":["gws"]},"cliHelp":"gws calendar +insert --help"}}

calendar +insert

PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.

create a new event

Usage

gws calendar +insert --summary <TEXT> --start <TIME> --end <TIME>

Target Calendar Rules

• Always state the active Google account and target calendar before writing.
• In multi-account setups, prefer an explicit --calendar <calendarId> instead of relying on primary.
• For this user's current setup, when the user says "my calendar" or gives no target, use --calendar [e-mail] after gws auth status confirms the active user is [e-mail].
• Do not write durable events to Apple Calendar, iCloud, or school calendars as a fallback.
• If multiple calendars share the same display name, list calendars and use the ID:

gws calendar calendarList list --params '{"showHidden":true,"maxResults":250}'

Flags

Flag	Required	Default	Description
--calendar	—	primary	Calendar ID (default: primary)
--summary	✓	—	Event summary/title
--start	✓	—	Start time (ISO 8601, e.g., 2024-01-01T10:00:00Z)
--end	✓	—	End time (ISO 8601)
--location	—	—	Event location
--description	—	—	Event description/body
--attendee	—	—	Attendee email (can be used multiple times)

Examples

gws calendar +insert --summary 'Standup' --start '2026-06-17T09:00:00-07:00' --end '2026-06-17T09:30:00-07:00'
gws calendar +insert --summary 'Review' --start ... --end ... --attendee [e-mail]

Tips

• Use RFC3339 format for times (e.g. 2026-06-17T09:00:00-07:00).
• For recurring events or conference links, use the raw API instead.

[!CAUTION] This is a write command — confirm with the user before executing.

See Also

• gws-shared — Global flags and auth
• gws-calendar — All manage calendars and events commands