Create an event
events_createCreate an event - schedule a meeting, book an appointment, block out time - in one of a connected account's own calendars: the one named by the calendarId calendars_list gives, else the account's default; a calendar only shared with the account is refused. Guests are invited by that account's provider: Microsoft or Google from the account's own address, Apple from its own address under the person's name, and a calendar server from the account's own address where it says it sends invitations, a meeting with guests refused elsewhere. A timed event's start and end are instants with their offset, the end no earlier than the start, so an entry of no length is taken; an all-day event's are dates, its end the day after its last. It is written in the person's own time zone, so an invitation shows that zone's time, and the answer gives its times in the zone it names under timeZone. A meeting with guests, no location and no video gets the person's default meeting link as its place. How it shows, its privacy, reminders, kind and video link are each refused with the reason where the account's provider lacks them. An Outlook subject takes at most 255 characters. repeat makes it a recurring series, each occurrence keeping the start's own hour in the person's time zone across clock changes. Who hears of it is notify's choice. Repeating a create whose answer was lost, with the same arguments, finds the event the first made rather than making a second - for the rest of that day (UTC), on Outlook only while Microsoft also recognises the repeat - so two events meant as two differ in some argument. Each guest's own times are answered under guestTimes in their time zone where it is known - the one guestZones names for them, else the one a member of the person's circles stored - and any other guest's zone as unknown, their time counted as the person's. A meeting any part of which falls, for a guest of known zone, outside 09:00-18:00 or on a Saturday or Sunday in that zone - an all-day one only on a Saturday or Sunday - is not sent: the refusal names each such guest and their time, and it goes out only once the call passes unusualHoursAgreed true on the person's word. A series is checked by its first occurrence; the person's own hours are never held.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end | Yes | ||
| body | No | ||
| kind | No | Google makes either only in a Workspace account's main calendar, timed; Outlook makes out of office alone, shown away. | |
| start | Yes | ||
| video | No | A Meet link on a Google account or a Teams link on a work Microsoft account, given back under joinUrl. | |
| guests | No | Addresses to invite. | |
| notify | No | Who the provider tells: every guest where omitted, externalOnly only guests outside Google Calendar, none nobody. Outlook tells every guest of a meeting it makes, changes or cancels, so there only an answer goes untold. | |
| repeat | No | Makes it a recurring series, from its start, without end unless until or count is named. | |
| showAs | No | How it shows; Google shows busy or free alone. Busy where omitted. | |
| account | Yes | The connected account, by the address calendars_list names. | |
| privacy | No | The calendar's own where omitted. | |
| subject | Yes | ||
| location | No | ||
| provider | No | The account's provider, as calendars_list names it; needed only where two connected accounts share an address. | |
| reminders | No | Minutes before its start each reminder sounds, Outlook keeping one; empty for none, the calendar's own where omitted. | |
| calendarId | No | The calendar to create it in, by the calendarId calendars_list names; the account's default where omitted. | |
| guestZones | No | A guest's own time zone, only as the person names it - never inferred from an address, a language or a provider. | |
| unusualHoursAgreed | No | True only once the person has agreed to send at the hours an answer named as unusual for a guest. |