Skip to content
Zoan Docs

Google Calendar — Connect

Google Calendar — Connect

Section titled “Google Calendar — Connect”

Type: googlecalendar-connect  ·  Package: Google Calendar v1.0.5  ·  Output: ZoanGoogleCalendarSession

Opens an authenticated session with Google Calendar. It is the package’s starting point: every other activity (create, update, search events, manage guests…) works on this session.

How it works

Section titled “How it works”

Authenticates with a Zoan Cloud Google OAuth connection (or a service account) and opens the session. Two ways to use it:

  • With body: the activities you place inside inherit the session automatically; when the block ends it closes by itself, also if an activity fails.
  • Without body: returns the session as output; save it in a variable, pass it in session to the other activities and close it with Google Calendar — Close.

When connecting it reads the main calendar to learn the account email, which Respond (RSVP) uses by default. If that lookup fails (expired token, no network), it does not stop: the error shows up on the first operation.

Required parameters

Section titled “Required parameters”

None.

Optional parameters

Section titled “Optional parameters”
ParameterTypeDefaultDescription
authTypestringoauthAuthentication mode: oauth or service-account.
credentialcredential—OAuth mode: the Zoan Cloud Google OAuth connection, credential("code-name").
serviceAccountcredential—Service account mode: credential with the full JSON key.
impersonateUserstring—Service account mode (optional): email of the Workspace user whose calendar is managed (domain-wide delegation).

Sub-flows

Section titled “Sub-flows”

body

Section titled “body”

Activities to run inside the session. They inherit the session automatically and it closes when they finish.

Output

Section titled “Output”

Without body, returns a ZoanGoogleCalendarSession: assign it to a variable and pass it as session to the other activities. With body it returns nothing (the session is inherited).

Common errors

Section titled “Common errors”
MessageCause and fix
Credential '…' could not be resolved. Verify it exists in Zoan Automation and that there is an active session.The connection or credential does not exist in the environment, the display name was used instead of the code name, or there is no Zoan Cloud session.
'credential' does not contain a valid access_token. Check the OAuth Connection in Zoan Cloud.The connection exists but has no token (for example, it is still Pending). Authorize it in Zoan Cloud.
'serviceAccount' must reference a Zoan Cloud credential containing the service account JSON key.In service account mode, the credential is empty.
The service account credential is not a valid Google service account JSON key. …The stored value is not the full JSON key. Store it again exactly as downloaded.

Example

Section titled “Example”
Google Calendar — Connect   credential = credential("calendar-team")
 └─ body:
      Google Calendar — Create event   summary = "Weekly meeting"
                                        start = "2026-06-15T14:30:00-05:00"   end = "2026-06-15T15:30:00-05:00"
                                        → output: ev
      Log   message = "Created: " + ev["htmlLink"]
Section titled “Related activities”