Google Docs
Read and append to Google Docs — notes, logs and content from your app. Connected with your own key — encrypted, server-side only, never exposed to the browser.
What you can build
Prompts like these, typed into opix, produce working Google Docs features.
Connect it in three steps
Create the key
Generate an API key in your Google Docs account — the link below takes you to the exact page.
Paste it in opix
Open your project → Connectors, paste the key. It's stored encrypted and injected server-side; even you only see the last four characters afterwards.
Prompt what you want
Describe the feature in chat — opix writes the Google Docs code with honest fallbacks built in.
Keys & setup
| Environment variable | Required |
|---|---|
| GOOGLE_SERVICE_ACCOUNT_KEY | Yes |
| GOOGLE_DOCS_DOCUMENT_ID | Optional |
Uses the same service-account JSON as Google Sheets/Drive. Share the target doc with the service account's email (client_email) as Editor. The default document id is optional — it's the long string in the doc's URL.
Honest by default
Apps built with opix never pretend. Without keys, doc-driven sections render a designed empty state with a connect note and write routes return 503.
Build with Google Docs today
Describe the app, connect your key, ship it.
Google Docs is a trademark of its respective owner, used for identification purposes only. opix is not affiliated with or endorsed by Google Docs.