n8n

How to Connect n8n to Google Docs: Automate Document Workflows (2025)

Rodrigo Ferreira

— 5 min read

Every business runs on documents: proposals, contracts, meeting notes, invoices, reports. And most of them are still made by hand — copy the last one, find-and-replace the client name, hope you didn't miss a field. That manual work is exactly what n8n plus the Google Docs API were built to eliminate. In this guide you'll learn how to connect n8n to Google Docs, set up the credentials properly, and build a real workflow that turns a form submission into a finished, personalized document that lands in someone's inbox automatically.

What the Google Docs node in n8n actually does

n8n ships with a native Google Docs node that talks directly to the Google Docs API. It doesn't screen-scrape or open a browser — it makes authenticated API calls, which means it's fast and reliable inside an automation. The node exposes a small but powerful set of operations:

  • Create — spin up a brand-new Google Doc, optionally inside a specific Drive folder.
  • Get — pull the full content and structure of an existing document as JSON.
  • Update — this is the workhorse. It sends a batch of requests to the doc: insert text, replace all instances of a string, insert tables, delete ranges, and more.

The key mental model: you rarely "build" a document from scratch with n8n. Instead you keep a template document full of placeholders like {{client_name}}, {{project_scope}}, and {{total_price}}, then copy it and use replaceAllText requests to swap the placeholders for real data. That approach preserves your fonts, logos, headers, and formatting — Docs stays the design tool, n8n just fills in the blanks.

Setting up Google OAuth2 credentials in n8n

Before the node works, n8n needs permission to act on your Google account. This is the step people get stuck on, so follow it precisely.

1. Create a Google Cloud project

Go to console.cloud.google.com, click the project dropdown, and create a new project (call it something like "n8n-automation"). Everything below happens inside this project.

2. Enable the right APIs

In APIs & Services → Library, search for and enable both the Google Docs API and the Google Drive API. You need Drive too, because creating docs, moving them into folders, and setting sharing permissions are all Drive operations.

Under OAuth consent screen, choose "External" (unless you're on Google Workspace and want "Internal"), give the app a name, and add your email as a test user. While the app is in "Testing" mode, only listed test users can authorize it — that's fine for a personal or team automation.

4. Create OAuth client credentials

Go to Credentials → Create Credentials → OAuth client ID, pick Web application, and — this is critical — add n8n's redirect URL to Authorized redirect URIs. n8n shows you the exact URL when you create the credential; it looks like https://your-n8n-domain/rest/oauth2-credential/callback. Copy the Client ID and Client Secret.

5. Add the scopes and connect

In n8n, create a new Google Docs OAuth2 API credential, paste in the Client ID and Secret, and make sure the scopes cover both editing docs and accessing Drive:

  • https://www.googleapis.com/auth/documents
  • https://www.googleapis.com/auth/drive

Click Connect my account, sign in through the Google popup, approve access, and you'll see "Account connected." That single credential now powers every Google Docs and Google Drive node in your instance.

Injecting dynamic data with expressions

The reason this whole setup is worth it is n8n expressions — the syntax that pipes data from earlier nodes into your document. Anywhere a field accepts an expression, you can reference incoming data like this:

  • {{ $json.email }} — a field from the current item.
  • {{ $('Form Trigger').item.json.company }} — a field from a specific earlier node.
  • {{ $now.format('yyyy-MM-dd') }} — today's date, formatted.

In a Docs Update operation, you use these inside "Replace All Text" actions: the search value is your placeholder ({{client_name}}) and the replace value is the expression pulling live data. That's the bridge between a static template and a finished, one-off document.

Skip the build: Document automation is the same engine that powers content automation — a single input fanned out into polished, ready-to-ship output. If you'd rather deploy a proven system than wire nodes yourself, the AI Content Factory turns one brief into a blog post, LinkedIn post, and tweet, all generated and published automatically. Get the AI Content Factory on Gumroad →

Step-by-step: form submission → personalized document → email

Here's a complete, concrete workflow you can build in about fifteen minutes. The goal: a prospect fills out a form, and a personalized proposal document gets generated from your template and emailed to them.

  1. Prepare the template doc. In Google Docs, create a proposal styled exactly how you want it. Where the variable content goes, type placeholders: {{client_name}}, {{project_scope}}, {{price}}, {{date}}. Note its document ID from the URL.
  2. Form Trigger node. Add an n8n Form Trigger with fields for name, email, company, scope, and budget. This gives you a shareable form URL and fires the workflow on submit.
  3. Google Drive node — Copy File. Don't edit your master template. Instead use the Google Drive node with the Copy operation: source is the template's file ID, and name the copy dynamically, e.g. Proposal — {{ $json.company }}. Optionally set the parent folder so it lands in your "Proposals" folder. This returns a new file ID.
  4. Google Docs node — Update. Point it at the new file ID from the copy step. Add several Replace All Text actions:
    • Search {{client_name}} → Replace {{ $('Form Trigger').item.json.name }}
    • Search {{project_scope}} → Replace {{ $('Form Trigger').item.json.scope }}
    • Search {{price}} → Replace {{ $('Form Trigger').item.json.budget }}
    • Search {{date}} → Replace {{ $now.format('MMMM d, yyyy') }}
  5. Google Drive node — Share / Export. Either set the doc's permission to "anyone with the link can view," or use Drive's Download operation to export the doc as a PDF binary.
  6. Gmail (or Send Email) node. Send the prospect a message: Hi {{ $('Form Trigger').item.json.name }}, here's your proposal. Attach the exported PDF or paste the shareable link.

Submit the form once to test. Within seconds you'll have a fully personalized document created, filled, and delivered — no copy-paste, no missed fields.

Combining the Google Drive node for folders and permissions

The Docs node handles content; the Drive node handles everything around the file. Because they share the same OAuth credential, they work together seamlessly. Common combinations worth knowing:

  • Organize automatically. Use Drive's Create Folder per client, then drop each generated doc inside it — your Drive stays tidy without manual filing.
  • Control access. Drive's Share operation sets who can view or edit. Give the client view-only, give your team edit rights, all in one node.
  • Convert formats. Drive can export a Doc to PDF or DOCX — essential for contracts and anything a client needs to sign or archive.

Three real use cases worth automating

1. Sales proposals

The example above. Every inbound lead gets a branded, personalized proposal in under a minute instead of an hour. Sales reps stop rebuilding the same document and spend their time following up instead.

2. Meeting notes and recaps

Trigger the workflow after a call — from a calendar event, a Fireflies/Otter transcript, or a Slack command. Feed the transcript through an AI node to summarize action items, then insert the summary into a dated "Meeting Notes" template and share it with attendees automatically.

3. Contracts and agreements

Keep contract templates with placeholders for party names, dates, amounts, and terms. When a deal is marked "won" in your CRM, n8n copies the contract template, fills the details, exports a PDF, and routes it to an e-signature tool. What used to be a legal-ops bottleneck becomes a two-minute automated step.

Tips to keep it reliable

  • Always copy, never edit the master. One accidental Update on your template and every future doc is broken.
  • Use unique placeholders. {{price}} is safer than price, which could accidentally match body text.
  • Watch API quotas. The Docs API has per-minute write limits; for high volume, batch your replace actions into a single Update call rather than many small ones.
  • Re-authorize if it breaks. If credentials expire or you add a scope, reconnect the account in n8n so the new token includes the right permissions.

Wrapping up

Connecting n8n to Google Docs turns your most repetitive document busywork into a background process. Set up the OAuth2 credential once with the Docs and Drive scopes, keep clean template documents with clear placeholders, and let the Copy → Update → Share pattern do the assembly. Whether it's proposals, meeting recaps, or contracts, the payoff is the same: consistent, personalized documents produced in seconds instead of hours.

Ready to automate? Get this template on Gumroad →

Read more