Google Docs
DocumentsCreate, read, edit, export, and generate Google Docs documents from templates through the Google Docs and Drive APIs. Agents fill placeholder tokens with workflow data to produce contracts, invoices, and reports, then export to PDF.
What This Integration Enables
Agents can create, read, edit, and export Google Docs as steps inside a larger workflow. The most common pattern is document generation: copy a template, replace tokens with real data, export to PDF, and pass the result downstream. Agents can also read a document's full plain text for summarization or AI processing, append content to a running log, and reach any advanced Docs operation through the raw Batch Update passthrough when a dedicated action does not cover it. The point is not that FlowRunner can write to a document. The point is that generating the document stops being a person's manual chore and becomes a governed step, with a human pulled in only when the finished document is about to leave the building.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Contract generated from deal data
A deal moves to the stage that needs a signed agreement. The agent reads the deal record from HubSpot, then calls Create From Template with the deal's company name, term, and pricing mapped to the template's `{{placeholders}}`. It checks the returned occurrence count to confirm every token was filled, then runs Export Document to produce a PDF in FlowRunner file storage. The finished contract is ready to route for signature through [DocuSign](/integrations/docusign). The work shifts from a rep hand-editing a Word file to an agent producing a consistent, verified document every time.
Meeting notes summarized and shared
A recurring meeting document needs a digest. The agent calls Get Document, which returns a convenience `text` field with the full body as plain text. It hands that text to an AI summarization step, then posts the summary to the team's [Slack](/integrations/slack) channel. Nobody copies the doc into a chat window and trims it down by hand. The running document stays the source of record and the summary reaches the people who need it.
Personalized welcome letters with a human gate
A new customer submits an onboarding form captured through [Google Forms](/integrations/google-forms). The agent generates a personalized welcome letter with Create From Template, then exports it to PDF. Because the letter carries the company's name and commitments to an outside party, the agent does not send it automatically. It pauses and asks the account owner to approve the wording. Once approved, the agent emails the PDF through [Gmail](/integrations/gmail-service). The routine drafting is automated; the judgment about what goes out under the company's name stays with a person.
Human-in-Loop Highlight
The consequential moment with Google Docs is not creating a document, it is sending a generated document to someone outside the company. When an agent produces a client contract or an offer letter from a template, it pauses before that document leaves the building and asks the owner through Slack: "The [Company] agreement is generated and exported to PDF. Term is 12 months, total is the value pulled from the deal record. Approve to send for signature, or flag a field to fix?" The owner approves or corrects. A generated document that is wrong in a placeholder is a document that goes out wrong to a customer, so the agent treats the external send as the point that needs human judgment, not the drafting that led up to it.
Agent Capabilities
9 actionsDocuments
3- Create Document Creates a new blank Google Docs document with a given title in the connected user's My Drive root, optionally inserting initial body text. Used when a workflow needs a fresh document to build up, such as a running log or a draft the agent will fill in later steps.
- Get Document Retrieves a document by ID and returns the raw Docs resource plus a convenience `text` field with the full body as concatenated plain text. Used when a workflow needs to read a document for summarization, analysis, or AI processing, or needs the body structure for index-based editing.
- Delete Document Permanently deletes a document from Google Drive by ID. The file is removed immediately without going to the trash and cannot be recovered. Used in cleanup workflows for temporary documents the agent created earlier in the same flow.
Text Editing
4- Append Text Appends text to the very end of a document body, using newline characters to create new paragraphs. Used to keep a running document current, such as adding each workflow run summary to a shared log.
- Insert Text Inserts text at a specific character index in the document body. Used when content must land at a known position rather than at the end, using the index bounds returned by Get Document.
- Replace All Text Replaces every occurrence of a text string with replacement text, with case-sensitive or case-insensitive matching. Used to update recurring values across a document or, with an empty replacement, to strip content out.
- Batch Update Executes a raw Google Docs batchUpdate request, the escape hatch for operations not covered by dedicated actions such as styling, tables, images, named ranges, and headers. Used when a workflow needs an advanced Docs operation applied atomically.
Templates
1- Create From Template Copies a template document through Google Drive, then replaces `{{placeholder}}` tokens with provided values and returns an occurrence count per placeholder. This is the primary action for generating contracts, invoices, offer letters, and personalized documents from workflow data.
Export
1- Export Document Exports a document to PDF, plain text, Word (DOCX), or HTML and saves the result to FlowRunner file storage, returning a stored-file URL. Used at the end of a generation workflow to produce a shareable file for emailing or archiving; the Drive export endpoint limits exported content to 10 MB.
Start building with Google Docs
$100 in credits. No card required. Connect in minutes.