Google Calendar

Read who can own the next implementation step, off the calendar.

Google Calendar
Google Calendar

Who can own the implementation next week.

A scene playing on a loop. Somebody says: Who can own the implementation next week.. The run reaches google-calendar, which returns list_calendars, 1; then google-calendar, which returns list_events, 9. Available owners, read off the calendar. Nothing booked.
Authorised by
Google OAuth, on the calendar you want read.
Reads
  • list_calendars
  • list_events
Writes
  • create_event

These are the rows it can call, and there are no others. Across 8 connectors, 14 capability rows write anything.

Where it stops

The primary calendar only, reading and writing both. It can put an event on it, and it cancels none and moves none. A listing refuses to run without a window, so nobody reads a whole account by leaving one out.

Finish the client call with the work already mapped.

Send one recent client meeting. Leave with the actions, follow-ups and exceptions a person can approve.