The Google Calendar integration gives Cora read-only access to your calendar so it can reference your upcoming meetings in chat and agents, and detect lifecycle events from completed customer meetings.

Integration Type: OAuth 2.0, User-Level
​Scope: Read-only (calendar.readonly)

This only grants read-only access to your calendar. Cora cannot modify, create, or delete any events.

Track events across your customer lifecycle, from onboarding and renewals to upsells, expansion, and churn risk, so your team never misses a key moment.

For Google Calendar, Cora watches completed meetings on the connected user's calendar. It uses the meeting title, description, attendees, and organizer to match each meeting to a customer account and apply your organization's detection rules. Cancelled meetings and meetings the connected user declined are not used.

On first connect, the Lifecycle Events toggle is enabled automatically. Once enabled, Cora syncs completed meetings from about the last 30 days and re-checks about once an hour. Which signal types appear is governed by your organization's Lifecycle Taxonomy. For setup details, see Setting Up Signals. For common questions, see the Signals FAQ.

Reads:

Cora does not create, modify, or delete any calendar events. Each user connects their own calendar. Cora only accesses the calendar of the user who authorized the connection.

When Lifecycle Events are enabled, Cora can also detect lifecycle events from completed calendar meetings and surface them as Signals. Detection is rule-based: Cora matches meetings to accounts by attendee or organizer email, either by an exact match to your CRM or by falling back to the email domain. Meetings that do not match a known account do not produce Signals. See Setting Up Signals and the Signals FAQ.

To disconnect Google Calendar:

You can also revoke access directly in your Google account settings at myaccount.google.com/permissions.