The A.B.C. NetworkThe A.B.C. Network
One-time setup

Connect Google to the A.B.C. Calendar

This is done once by the account owner. After it, staff press Connect Google and the calendar syncs both ways, adds Meet links, attaches Drive files, exports to Docs and Sheets, and sends invites through Gmail.

Checking status
Open calendar
1

What Mr. Howard provides

Create these in Google Cloud Console under one project for The A.B.C. Network. They are entered through the secure form, never by email or chat.

  1. OAuth 2.0 Client ID (type: Web application)
  2. OAuth 2.0 Client secret for that client
  3. API key restricted to the Google Picker API and to this website (needed only for the Drive file picker)
  4. Project number (used as the Picker app ID)
2

Paste these into the OAuth client

When the calendar goes live, add the live site's matching URI and origin too.

3

Turn on these APIs

Google Calendar APIGoogle Drive APIGoogle Picker API
4

OAuth consent screen

App name: The A.B.C. Network. Support email: aibusinessrankers@gmail.com. Add these scopes:

    The calendar scope is sensitive, so Google lists the app as Testing until it is verified. In Testing, add each staff Google account as a test user. Drive access is limited to files the app creates or that staff pick.

    5

    What happens next

    The team stores the values on the server with owner-only access, then this page shows Ready to connect. A staff member signs in on the calendar and presses Connect Google. Existing sessions upload to Google Calendar and Google events flow back every 5 minutes or on Sync now. Docs and Sheets exports use the Drive API, so no extra APIs are needed.