Google Docs

​

Prerequisites

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

​

Setup

​

Option 1: Interactive CLI

healops integrations setup

​

Option 2: Environment variables

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

​

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"
      }
    }
  ]
}

​

Creating a service account

1. In Google Cloud Console, go to IAM & Admin → Service Accounts
2. Click Create Service Account
3. Give it a name (e.g., healops-docs) and click Create
4. Skip role assignment and click Done
5. Click on the service account → Keys → Add Key → Create new key (JSON)
6. Download the JSON file

​

Granting Drive folder access

1. In Google Drive, open the folder where reports should be saved
2. Click Share
3. Add the service account email (e.g., healops-docs@your-project.iam.gserviceaccount.com)
4. Set the permission to Editor

​

Finding the folder ID

​

Verify

healops integrations verify google_docs

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

​

Troubleshooting

​

Security best practices

• 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.