Update
Native Google Sheets export — no third-party connector required
TL;DR
Reports and data pulls now export directly to Google Sheets as a first-party integration. It uses the `drive.file` scope — access limited to files the app itself creates — which is both the correct permission for an export tool and the reason the feature needed no restricted-scope security assessment.
What shipped
- Direct export to a real Google Sheet, created by the agent, in one step.
- Update-in-place, so a recurring export refreshes the same sheet rather than littering your Drive with copies.
- Uses `drive.file` — the app can only touch files it created, never the rest of your Drive.
Why the scope choice matters
The convenient option would have been a broad Drive read scope. That sits in Google's restricted tier and requires a third-party security assessment — and it would grant far more access than an export tool has any business holding. The narrow scope is both cheaper to ship and the right permission.
Frequently asked questions
- Can the agent read my other Google Drive files?
- No. The integration uses the drive.file scope, which grants access only to files the app itself creates. Everything else in your Drive is out of reach.
- Does a recurring export create a new sheet every time?
- No — it updates the same sheet in place.