Skip to main content
Google Calendar uses the same Google OAuth app as Gmail, but it is a separate connection with its own consent. Set up the server once with Gmail & Google Calendar, then connect Google Calendar from Integrations.

​
How it works

Every 30 minutes OpenNous reads each connected calendar from 1 day back to 30 days ahead, plus a longer look back when you first connect. Each event with someone from outside your team becomes a meeting on that person’s timeline:
  • meeting_scheduled for an upcoming meeting, and meeting_held once it has happened.
  • A moved meeting adds a “Rescheduled” marker on the old slot and logs the new time.
  • A cancelled upcoming meeting adds a “Cancelled” marker.
Each event is recorded once per person (keyed on the Google event id), so re-reading a calendar never duplicates anything.

​
Who gets a record

  • Anyone already in OpenNous is matched by email.
  • A new attendee is created only when their email domain belongs to a company you already track. Personal addresses (gmail.com and similar) are never created.
  • Your own team is never treated as a lead.
  • Scheduler and no-reply addresses (Calendly, Zoom Scheduler, resource calendars) are ignored.
  • All-day events are skipped.

​
Setup

  1. As the server admin, configure the Google OAuth app (steps). Calendar uses the calendar.readonly scope.
  2. In OpenNous, go to Integrations, click Add → Google Calendar → Connect with Google, and approve read-only calendar access.

​
Environment variables

These are set for the whole server, not per workspace.