Google Docs
Create, read, and apply structured edits to Google documents
Connect Google Docs when a project needs to create documents, read their structure, or apply Google Docs API update requests through a shared or published app-user account.
Available operations
| Operation | What it does | Limit per minute |
|---|---|---|
create_document | Creates a document with a title | 60 |
get_document | Reads one document by ID | 60 |
batch_update | Applies a bounded list of structured document updates | 60 |
The connection requests Google Docs access plus project-files access in Drive. It can work with documents created or opened through the connection; it does not grant unrestricted discovery of every Drive file.
Connect Google Docs
An administrator must configure the Google OAuth app and enable Google Docs under Admin > Settings > Integrations. Ask the AI for a concrete document workflow. Examples:
- “Create a weekly report in our Google account and insert these sections.”
- “Let each signed-in user connect Google Docs and create a document from a form.”
Choose an existing connection or select Connect new and authorize Google. Use published app-user mode when each user owns their documents.
Verify Google Docs
- Create a document with a unique test title.
- Read it and confirm the returned document ID and title.
- Apply one
batch_update, such as inserting a short marker at the document start. - Open the document in Google Docs and confirm the marker.
- Remove the test document in Google Drive.
batch_update accepts Google Docs API request objects. Invalid indexes, unsupported request shapes, or stale write controls are rejected by Google. Read the document again, rebuild the smallest valid update, and retry once.
Keep generated connector calls on the server. Disconnecting stops future Swarmz access and does not delete documents or reverse edits.