# Google Docs AI integration on Definable

> Google Docs is a cloud-based word processor with real-time collaboration, version history, and integration with other Google Workspace apps

## What this connects

Google Docs is a cloud-based word processor with real-time collaboration, version history, and integration with other Google Workspace apps

Vendor: https://docs.google.com

## Tools available

**33** tools available. First 12:

- `GOOGLEDOCS_COPY_DOCUMENT` — Copy Google Document — Tool to create a copy of an existing Google Document. Use this to duplicate a document, for example, when using an existing document as a template. The copied document will have a default title (e.g., 'Copy of [original title]') if no new title is provided, and will be placed in the user's root Google Drive folder.
- `GOOGLEDOCS_CREATE_DOCUMENT` — Create a document — Creates a new Google Docs document using the provided title as filename and inserts the initial text at the beginning if non-empty, returning the document's ID and metadata (excluding body content).
- `GOOGLEDOCS_CREATE_DOCUMENT2` — Create blank document (Deprecated) — DEPRECATED: Use GOOGLEDOCS_CREATE_DOCUMENT instead. Tool to create a blank Google Docs document with a specified title. Use when you need to create a new, empty document.
- `GOOGLEDOCS_CREATE_DOCUMENT_MARKDOWN` — Create Document Markdown — Creates a new Google Docs document, optionally initializing it with a title and content provided as Markdown text.
- `GOOGLEDOCS_CREATE_FOOTER` — Create Footer — Tool to create a new footer in a Google Document. Use when you need to add a footer, optionally specifying its type and the section it applies to.
- `GOOGLEDOCS_CREATE_FOOTNOTE` — Create Footnote — Tool to create a new footnote in a Google Document. Use this when you need to add a footnote at a specific location or at the end of the document body.
- `GOOGLEDOCS_CREATE_HEADER` — Create Header — Tool to create a new header in a Google Document, optionally with text content. Use this tool when you need to add a header to a document. You can provide: - document_id: The ID of the document (required) - type: The header type (DEFAULT is the standard header) - text: Optional text content to add to the header - section_break_location: Optional location for section-specific headers
- `GOOGLEDOCS_CREATE_NAMED_RANGE` — Create Named Range — Tool to create a new named range in a Google Document. Use this to assign a name to a specific part of the document for easier reference or programmatic manipulation.
- `GOOGLEDOCS_CREATE_PARAGRAPH_BULLETS` — Create Paragraph Bullets — Tool to add bullets to paragraphs within a specified range in a Google Document. Use when you need to format a list or a set of paragraphs as bullet points.
- `GOOGLEDOCS_DELETE_CONTENT_RANGE` — Delete Content Range in Document — Tool to delete a range of content from a Google Document. Use when you need to remove a specific portion of text or other structural elements within a document. Note: Every segment (body, header, footer, footnote) in Google Docs ends with a final newline character that cannot be deleted. Ensure the endIndex does not include this trailing newline.
- `GOOGLEDOCS_DELETE_FOOTER` — Delete Footer — Tool to delete a footer from a Google Document. Use when you need to remove a footer from a specific section or the default footer.
- `GOOGLEDOCS_DELETE_HEADER` — Delete Header — Deletes the header from the specified section or the default header if no section is specified. Use this tool to remove a header from a Google Document.

## Auth

Auth schemes: `OAUTH2`. Managed by Definable: `OAUTH2` — no client credentials required from the user.

## How agents use Google Docs

Inside a Definable workflow, Google Docs is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Google Docs** — the Researcher (GPT-5.5) pulls context from Google Docs (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Google Docs** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Google Docs (create record, post message, draft email).
- **Designer / Engineer → Distributor → Google Docs** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Google Docs (attach file, open PR comment, post status).

The Verifier checks every Google Docs call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- documents — https://definable.ai/apps/category/documents/

## Related

- HTML page: https://definable.ai/apps/googledocs/
- Same category (documents): https://definable.ai/apps/category/documents/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt