Google Docs - OpenSRE Documentation

Overview

OpenSRE can write investigation findings directly to Google Drive as formatted Google Docs — creating a persistent, shareable record of each incident investigation linked to your team’s existing Drive folder.

Prerequisites

Google Cloud project with the Google Drive API enabled
Service account with access to a shared Drive folder

Setup

There is no dedicated opensre integrations setup google_docs command today. Configure Google Docs through the onboarding wizard, environment variables, or the persistent store.

Option 1: Onboarding wizard

opensre onboard

Select Google Docs when prompted and provide your credentials file path and folder ID.

Option 2: Environment variables

Add to your .env:

GOOGLE_CREDENTIALS_FILE=/path/to/service-account.json
GOOGLE_DRIVE_FOLDER_ID=your-google-drive-folder-id

Variable	Default	Description
`GOOGLE_CREDENTIALS_FILE`	—	Required. Path to the service account JSON file
`GOOGLE_DRIVE_FOLDER_ID`	—	Required. Google Drive folder ID for investigation reports

Option 3: Persistent store

{
  "version": 1,
  "integrations": [
    {
      "id": "google-docs-prod",
      "service": "google_docs",
      "status": "active",
      "credentials": {
        "credentials_file": "/path/to/service-account.json",
        "folder_id": "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms"
      }
    }
  ]
}

Credentials

Creating a service account

In Google Cloud Console, go to IAM & Admin → Service Accounts
Click Create Service Account
Give it a name (for example opensre-docs) and click Create
Skip role assignment and click Done
Click on the service account → Keys → Add Key → Create new key (JSON)
Download the JSON file

Auth uses a service account only (Google Docs + Drive API scopes) — not end-user OAuth.

Granting Drive folder access

In Google Drive, open the folder where reports should be saved
Click Share
Add the service account email (for example opensre-docs@your-project.iam.gserviceaccount.com)
Set the permission to Editor

Finding the folder ID

The folder ID appears in the Drive URL: https://drive.google.com/drive/folders/<folder-id>

Investigation tools

Tool	What it does
`create_google_docs_incident_report`	Creates a Google Doc in the configured Drive folder and inserts the investigation / postmortem content. Can optionally share the doc (`reader` / `writer` / `owner`).

Verify

opensre integrations verify google_docs

Expected output:

Service: google_docs
Status: passed
Detail: Connected to Drive folder 1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms (3 items in folder)

Verification probes Drive access to the configured folder.

Troubleshooting

Symptom	Fix
Credentials file not found	Check the path in `GOOGLE_CREDENTIALS_FILE` — use an absolute path
403 Forbidden	The service account hasn’t been added to the Drive folder with Editor access
Drive API not enabled	Enable the Google Drive API in your Google Cloud project
Folder not found	Confirm the folder ID and that the service account has access

Security

Keep the service account JSON file outside of your repository — add it to .gitignore.
Grant the service account access only to the specific Drive folder it needs.
Rotate the service account key periodically via Google Cloud Console.

​Overview

​Prerequisites

​Setup

​Option 1: Onboarding wizard

​Option 2: Environment variables

​Option 3: Persistent store

​Credentials

​Creating a service account

​Granting Drive folder access

​Finding the folder ID

​Investigation tools

​Verify

​Troubleshooting

​Security