Live DemoDownload Free

Configuration

Google Connect Setup

Prepare Google OAuth for Calendar, Tasks, and supported Drive file workflows in Zimphony Webmail.

What Google Connect uses

Google Connect is optional and user initiated. It is used only for Calendar, Tasks, and supported Drive file workflows. It does not access Gmail mailbox messages.

  • View and manage Google Calendar events from Webmail.
  • Create and update Google Tasks and notes.
  • Select and use supported Google Drive files in Webmail.
  • Attach supported files from Google Drive.
  • Save supported files to Google Drive.
  • Insert or send Google Drive links.

Google Connect does not provide Gmail reading, import, sync, or sending through Gmail. It also does not provide Google Drive permission-management administration or folder permission-management UI.

  1. 01

    Create a Google Cloud project

    Create or select the Google Cloud project that will provide OAuth access for your Zimphony deployment.

  2. 02

    Enable the required APIs

    Enable these APIs in the project:

    • Google Calendar API
    • Google Drive API
    • Google Tasks API
  3. 03

    Configure Google Auth

    Configure the OAuth consent experience for the intended users and production context. The current release requests these scopes:

    https://www.googleapis.com/auth/calendar
https://www.googleapis.com/auth/tasks
https://www.googleapis.com/auth/drive

    The Drive scope supports file selection, attachment, save-to-Drive, and link workflows in Webmail. It is not Gmail access or Drive permission-management administration.

    A future Zimphony release may use a more limited Drive file scope. Follow the release-specific documentation instead of replacing the current Drive scope on your own.

  4. 04

    Create the OAuth client

    Create an OAuth client with application type Web application.

  5. 05

    Configure the Authorized Redirect URI

    Add the exact redirect URI for the Zimphony Webmail hostname:

    https://<WEBMAIL_HOST>/calendar/oauth/callback

    For example:

    https://mail.example.com/calendar/oauth/callback

    Replace the example with the actual WEBMAIL_HOST. The value must match exactly.

  6. 06

    Obtain the client credentials

    Copy the values needed by the Zimphony installer:

    GOOGLE_CLIENT_ID=<google-client-id>
GOOGLE_CLIENT_SECRET=<google-client-secret>

    Treat the Client Secret as sensitive. Never place a real secret in public documentation or source control.

  7. 07

    Continue Zimphony installation

    Return to Installation and provide the Client ID and Client Secret when prompted.

    The installer derives the Calendar webhook endpoint from WEBMAIL_HOST:

    https://<WEBMAIL_HOST>/calendar/webhook

    This endpoint is used for Google Calendar push notifications. You do not need to invent or manually change it for the standard deployment.