Google Docs Action
Creates and edits Google Docs from a flow. Five operations, and the useful pattern behind them is the same one every time: keep a document with placeholders in it, copy it, and let the flow replace the placeholders with real values.
Setup
A Google credential with the documents scope. To put the new file in a particular folder, the same connection needs Drive access too.
Mode — action or AI toolkit
The Mode selector decides who drives the node. In Action mode you pick one operation and fill its fields, and the node does that every time it runs. In AI toolkit mode the operations become tools an AI Node can call, and the model chooses which one and with what arguments.
Operations
The Operation dropdown decides what the node does and which fields appear under it. These are the exact values the API validates against:
| Value | In the dropdown | What it does |
|---|---|---|
| readDoc | Read Document | Get document content as plain text |
| createDoc | Create Document | Create a new Google Doc |
| appendText | Append Text | Add text to end of document |
| replaceText | Replace Text | Find and replace text in document |
| insertTable | Insert Table | Insert a table at end of document |
Gotchas
- Replacing text is literal. The placeholder has to match exactly, so a template that says
{{name}}and a flow that writes{{Name}}silently changes nothing. - Appending adds at the end of the body, after any existing content — not at the cursor, because there is no cursor.
- Reading a document returns plain text. Formatting, tables and images do not survive the trip; if the flow needs structure, keep it in the payload rather than in the document.
- A document is not a spreadsheet. For tabular output the node you want is Google Sheets, not this one.