> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your app to Google Workspace

> Connect your app to Google Workspace to read and send email, manage calendars, store and create files, and use Google tools like Sheets, Docs, and Slides as part of your app's workflows.

export const connector_0 = "Google service"

[Google Workspace](https://workspace.google.com/) includes services like Gmail, Google Sheets, Google Calendar, Google Drive, Google Docs, and Google Slides. The Google Workspace connectors enable your Lovable app to securely access and manage data from these services using your Google account.

| Use                                                     | If you want to                                                                                              |
| ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| **App + chat connector** (this page)                    | Work with a shared Google Workspace connection in the chat and in your published apps                       |
| [App user connector](/integrations/app-user-connectors) | Let each user of your published app connect their own Google Workspace account and work with their own data |

With Google Workspace, your app can:

* Send and read emails with **Gmail**
* Read and update spreadsheet data in **Google Sheets**
* Create and manage **Google Calendar** events
* Upload, organize, and retrieve files from **Google Drive**
* Generate and edit documents in **Google Docs**
* Create and update presentations in **Google Slides**

Each connection is authorized for a single Google account. You can create multiple connections to work with multiple accounts or environments.

<Tip>
  Building an app that embeds an editable Google Doc, Sheet, or Slides deck? See [Edit Google Docs, Sheets, and Slides in Lovable](/tips-tricks/google-workspace-editing) for the recommended iframe URLs and a copyable knowledge file.
</Tip>

## Common use cases and example apps

These examples show both single-service apps and multi-service workflows. You can combine Google connectors within the same project to build more advanced automation and internal tools.

| Example app                   | Example prompt                                                                                                           | Description                                                                                                                                                                                             |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Sheets-powered CRM            | *Build a simple CRM that reads contacts from this Google Sheet and lets me add and edit rows.*                           | **Manage structured customer data using Google Sheets as a backend.**<br />The app reads contact records from a spreadsheet, displays them in a clean interface, and writes updates back automatically. |
| Team booking page             | *Build a booking page that checks our Google Calendar availability and creates events when someone books.*               | **Let users schedule time based on real calendar availability.**<br />The app checks free/busy data, shows open time slots, and creates calendar events when a booking is confirmed.                    |
| Transactional email sender    | *When a user submits this form, send them a confirmation email through Gmail.*                                           | **Send automated emails directly from your app**. <br />The app formats submission details and sends confirmation or notification emails through the connected Gmail account.                           |
| Drive-based file hub          | *Build an internal tool that lists our Drive folders and lets me upload and organize files.*                             | **Create a structured file management experience on top of Google Drive.**<br />The app lists folders and files, supports uploads, and keeps documents organized without leaving the interface.         |
| Proposal generator            | *Generate a Google Doc proposal from this form and save it to a specific Drive folder.*                                  | **Automate document creation from structured input.**<br />The app generates a formatted Google Doc using form data and saves it to the appropriate Drive folder for sharing or review.                 |
| Slide deck builder            | *Turn this project brief into a Google Slides presentation with a title slide and bullet points.*                        | **Turn structured content into a starter slide deck.**<br />The app generates a basic Google Slides deck from your content as a starting point for further editing and styling.                         |
| Expense tracker with receipts | *Build an expense tracker where receipts are uploaded to Drive and logged in a Google Sheet.*                            | **Combine file storage and structured tracking in one workflow.**<br />The app uploads receipt files to Drive and logs expense details in Sheets, linking each file to its corresponding record.        |
| CRM with email history        | *Show contacts from my Google Sheet and display the latest emails exchanged with them from Gmail.*                       | **Enrich contact records with real communication history.**<br />The app pulls related Gmail conversations and displays them alongside structured CRM data.                                             |
| Weekly report automation      | *Every Monday, read last week's metrics from Google Sheets and email a summary via Gmail.*                               | **Deliver recurring reports automatically.**<br />The app reads data from Sheets, generates a summary, and emails it to stakeholders on a schedule.                                                     |
| Meeting notes automation      | *After a Google Calendar event ends, generate meeting notes and save them as a Google Doc in Drive.*                     | **Turn meetings into structured documentation.**<br />The app reads calendar event details, generates organized notes, and saves them as a Google Doc in Drive.                                         |
| Client onboarding workflow    | *When a new client is added to my Google Sheet, generate a proposal Doc and kickoff Slides deck and save both to Drive.* | **Automate multi-step onboarding workflows.**<br />The app uses structured client data to generate documents and presentations, storing them in Drive for immediate use.                                |

## How Google Workspace connections work

Google Workspace connections are workspace-level integrations managed by workspace admins or owners. Admins and owners control which services the workspace connects and which permissions (scopes) each connection uses. This connector uses a single shared Google account for everyone who uses the app. If you need each end user to sign in with **their own** Google account and act on their own data, use an **[app user connector](/integrations/app-user-connectors)** instead.

All Google Workspace connectors use OAuth 2.0 to securely connect to your Google account. When you create a connection, you sign in with Google and authorize Lovable to access specific services on your behalf.

Within your Lovable workspace:

* You can create multiple connections per Google service.
* Each connection is a separate OAuth authorization tied to a Google account.
* Each connection can use different scopes (permissions), so you can control exactly what the connection can access.
* Multiple projects within a single workspace can use the same connection.

This makes it easy to separate environments (for example, development and production) or connect different Google accounts for different purposes.

Google Workspace connectors use Lovable's gateway architecture for secure OAuth handling and automatic token refresh. See [Gateway-based connectors](/integrations/app-connectors#gateway-based-connectors) for details on authentication and usage limits.

<Warning>
  **Connections are tied to a specific Google account**

  Each Google Workspace connection is authorized using the Google account that signs in during setup.

  For example:

  * If you connect Gmail using `employee@company.com`, emails sent through that connection will be sent from `employee@company.com`.
  * If you connect Google Calendar with your account, events will be created on your calendar.
  * Files created in Drive, Docs, or Slides will be owned by the connected account.

  Although the connection is available across the workspace, it always operates on the data of the Google account that authorized it.

  If your team needs to use a shared mailbox, shared calendar, or dedicated service account, make sure you authenticate using the appropriate Google account when creating the connection.
</Warning>

## How to connect a Google Workspace service

Workspace **admins** and **owners** can connect Google Workspace services.

When a connection is created, it becomes available across all projects in the workspace.

### Prerequisites

* A Google account with access to the service you want to connect
* Lovable workspace admin or owner role

### Set up your Google connection

<Steps>
  <Step title="Navigate to the desired Google connector">
    Go to **Connectors** and select the Google service you want to connect (for example, **Google Sheets**).
  </Step>

  <Step title="Add a new connection">
    Click **Add connection**.
  </Step>

  <Step title="Name the connection">
    In **Display name**, name the connection (for example, `Google Sheets – Production`).
  </Step>

  <Step title="Configure scopes (optional)">
    Expand **Advanced settings** to view and configure scopes — the Google API permissions your app needs. Default scopes are pre-selected for common use cases.

    <Tip>
      Select only the scopes your app needs. You can update scopes later by editing the connection and clicking **Reconnect**. For full scope documentation, see the [scope reference for each Google service.](https://developers.google.com/workspace/products)
    </Tip>
  </Step>

  <Step title="Connect to Google and authorize the connection">
    * Click **Connect**. The Google sign-in window opens — make sure your browser doesn't block pop-ups.
    * Sign in with the Google account you want to use, review the requested permissions, and click **Allow**. You'll be redirected back to Lovable with a confirmation.
  </Step>
</Steps>

When connected, your Lovable apps can start using the selected Google service.

## Connecting multiple Google services

If your app needs to use several Google services (for example, reading data from Sheets and sending results via Gmail), you can create a separate connection for each service.

Each connector has its own OAuth flow and scopes, so they are configured independently.

You can:

* Connect multiple services to the same Google account
* Use different Google accounts for different services
* Create separate connections for development and production

## Manage your {connector_0} connection

Connections are managed from [**Connectors**](https://lovable.dev/dashboard?connectors): select **{connector_0}**, then open the connection.

* **Unlink projects** to remove {connector_0} access from specific projects while keeping the connection available for others. See [Unlink projects from a connection](/integrations/app-connectors#unlink-projects-from-a-connection) for the steps.
* **Delete the connection** to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use {connector_0} stop working until a new connection is added. See [Delete a connection](/integrations/app-connectors#delete-a-connection) for the steps and who can delete.