What does the n8n Google Docs node do?

Document → Create, Get and Update. Update takes a list of actions on objects such as text, tables, page breaks and headers; for text the actions are Insert and Find and Replace Text, which covers most Pipedream Docs actions.

Is there a Google Docs trigger?

No. Use the Google Drive Trigger on the folder that holds the documents; it fires on new or changed files, including Docs.

How do I fill a template document?

Copy the template with Google Drive → File → Copy, then use Google Docs → Update with a Find and Replace Text action for each placeholder.

Do Docs steps convert automatically?

Not yet. They come through as marked placeholders with the document ID and text; the rebuild is one Google Docs node per step.

Pipedream Google Docs steps in n8n

Updated 2026-10-21 · 3 min read · n8n: Google Docs (Native n8n node)

Google Docs steps in Pipedream do one of two things: generate a document from a template (contracts, reports, proposals) or read a document's text to send it somewhere else. n8n's native Google Docs node handles both, with the Google Drive node covering the file side.

The n8n Google Docs node

n8n-nodes-base.googleDocs, resource Document:

Create – a new document with a title, optionally in a folder.
Get – the document, with an option to return simplified plain text.
Update – a list of actions applied in one request. Each action picks an object (Text, Table, Table Row, Table Column, Page Break, Paragraph Bullets, Header, Footer, Named Range, Positioned Object); for Text the actions are Insert and Find and Replace Text.

There is no Google Docs trigger. Anything the node does not cover goes through HTTP Request with the Google Docs credential (documents.batchUpdate).

What maps where

Pipedream (app `google_docs`)	In n8n	Status
Create Document	Google Docs → Document → Create	manual
Get Document	Document → Get (Simplify on for plain text)	manual
Append Text, Insert Text	Document → Update, Text → Insert (at end or at index)	manual
Replace Text	Document → Update, Text → Find and Replace Text	manual
Find Document	Google Drive → File/Folder → Search, filter by MIME type	manual
Create Document From Template	Google Drive → File → Copy, then Docs → Update with Find and Replace Text	manual, 2 nodes
New Document Created (Instant), New or Updated Document (Instant)	Google Drive Trigger on the folder	manual
Code step using `googleapis` docs client	Code node; token variable and package listed in the report	automatic, review

Google Docs actions are not in the converter's automatic list; the free report shows each step with its document ID and text so the rebuild is quick.

Credentials

The Google Docs node uses n8n's Google credentials:

OAuth2 (single service) – enable the Google Docs API (and the Drive API if you also copy or search files) in your Google Cloud project, create an OAuth client, add n8n's redirect URL. On n8n Cloud you can use the managed sign-in.
Service Account – supported for Docs. Share the template and the target folder with the service account email.

Pipedream's Google connection is not exportable; you connect again.

Typical migration: proposal generator

Pipedream: HTTP trigger (form) → Create Document From Template → Gmail send with the link. n8n: Webhook → Google Drive → Copy (template) → Google Docs → Update (Find and Replace Text for {{client}}, {{price}}, {{date}}) → Gmail → Send. Four nodes, two credentials (Google Drive and Docs, Gmail).

Pitfalls

Quotas. The Docs API allows 3,000 reads and 600 writes per minute per project, and 300 reads and 60 writes per minute per user. Over that you get 429; retry with backoff. Batch several Find and Replace Text actions into one Update call instead of one call per placeholder.
Placeholder collisions. n8n expressions use {{ }} too. If your template placeholders look like {{client}}, type them as plain text in the Old Text field (fixed mode), not inside an expression.
Index-based inserts shift after every insert; insert from the end backwards, or use Find and Replace Text.
7-day tokens for External apps in Testing status apply here as with all Google nodes.
Formatting. The node inserts plain text. Bold, links and styles need a raw batchUpdate request via HTTP Request.

How to move your Google Docs workflows

Export from Pipedream.
Upload on /convert; the free report lists the Docs steps and the credentials.
Download the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the Pipedream to n8n guide and the code step checker. Related: Google Drive, Google Sheets, WordPress.

FAQ

What does the n8n Google Docs node do?: Document → Create, Get and Update. Update takes a list of actions on objects such as text, tables, page breaks and headers; for text the actions are Insert and Find and Replace Text, which covers most Pipedream Docs actions.
Is there a Google Docs trigger?: No. Use the Google Drive Trigger on the folder that holds the documents; it fires on new or changed files, including Docs.
How do I fill a template document?: Copy the template with Google Drive → File → Copy, then use Google Docs → Update with a Find and Replace Text action for each placeholder.
Do Docs steps convert automatically?: Not yet. They come through as marked placeholders with the document ID and text; the rebuild is one Google Docs node per step.