Google Calendar Actions Land on Connector-Worker

Google Calendar joins Gmail and Sheets as a workflow action. Two new capabilities — calendar.events.list and calendar.events.insert — let a workflow check what's on a connected calendar or add a new event to it, whether that's booking a follow-up after a form submission or checking availability before a step runs.

Rides the existing Google connection

If you've already connected a Google account for Gmail or Sheets actions, Calendar needs nothing new from you to start working — it reuses the same OAuth connection, the same token-refresh handling, and the same action-registry shape those actions already use. There's no second "connect Calendar" flow to click through.

Under the hood, this did require widening what the platform asks Google for: the connection's requested scope now includes calendar access alongside Gmail and Sheets. If you connected Google before this shipped, Google will prompt you once for incremental consent the next time a Calendar action needs to run — that's Google's normal behavior for a scope that wasn't part of the original grant, and it happens automatically, not something Piskes has to build.

One honest caveat

Google's OAuth consent screen shows users a list of what a connected app can access, and that list is reviewed by Google (CASA review) when it changes. Adding Calendar access means that reviewed list is now a step behind what the connection actually requests — the same situation Gmail and Sheets scopes were already in before their own review caught up. It doesn't block Calendar actions from working today, but it's a housekeeping step still owed on Piskes' side.

What this unlocks

Combined with the existing Gmail and Sheets actions, a workflow can now read an email, log it to a spreadsheet, and put a follow-up on the calendar — three different Google surfaces, one connection, no separate integration to configure for each.