Connect company-owned Google Sheets to the CRM workflow.
See how Workspace connects Google OAuth, creates or locates a private lead sheet, writes validated CRM rows, and handles account-controlled access.
Connection comes before lead storage
A company member with the required integration permission initiates Google OAuth. Workspace associates the resulting connection with the company context and checks that connection before Drive-dependent CRM operations.
Production use also depends on correct Google Cloud consent-screen configuration, authorized domains, redirect URIs, requested scopes, and any Google verification requirements.
One ownership rule for manual and imported leads
Both CRM form submissions and validated spreadsheet imports follow the connected account's Google Sheet storage model.
- The user connects Google before creating or importing CRM leads.
- Workspace creates or resolves the company lead sheet through server routes.
- Imported data is parsed and validated before rows are sent to Google Sheets.
- CRM actions require company membership and the relevant CRM or integration permission.
Account control and operational boundaries
The connected Google account controls the Drive file, its sharing settings, and whether Workspace remains authorized. Revoking access prevents future authenticated operations until the company reconnects.
Google quotas, account storage, service availability, and OAuth policy remain external dependencies and should be monitored separately from the Workspace application database.