How does OCNORA authenticate with Google Calendar?

With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.

What can I automate with Google Calendar?

7 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.

What if the Google Calendar operation I need is not listed?

Where Google Calendar has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.

Are there templates that use Google Calendar?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Google Calendar calls controlled?

Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

Google Calendar

Business appsOAuth 2.0Connection test available

Create and list Google Calendar events (OAuth2).

OCNORA ships 7 typed Google Calendar operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.

Ask about Google Calendar Google Calendar API docs ↗

Before you connect Google Calendar

Authentication: OAuth 2.0
Credential: {"client_id", "client_secret", "refresh_token"}
Connection test: Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.

What you can do with Google Calendar

Operations, grouped by what they do to your data, plus 1 trigger that start a run.

Create and send 1

Create Event

Read and search 3

A sample Google Calendar workflow

1
Event Changetrigger.google_calendar_event
Start a run when an event is created, updated, or is about to start.
2
Get Eventgoogle_calendar.get_event
Read a single Google Calendar event by id.
3
Create Eventgoogle_calendar.create_event
Create an event on a Google Calendar.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.

Triggers 1

Event Change
Start a run when an event is created, updated, or is about to start.
trigger.google_calendar_event

Operations 7

Google Calendar questions

How does OCNORA authenticate with Google Calendar?: With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
What can I automate with Google Calendar?: 7 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
What if the Google Calendar operation I need is not listed?: Where Google Calendar has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use Google Calendar?: Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Google Calendar calls controlled?: Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first Google Calendar workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.

Book a technical demo Talk to sales