Resources · n8n integration

Google Docs n8n integrationAutomate Google Docs with n8n.

Need a workflow that writes a Google Doc on its own? The Google Docs n8n integration covers 3 operations on a single resource: create a document, read it, edit it. Nothing on the Google side starts the run, so a Schedule or Webhook node does, for ops and marketing teams done with copy-paste.

Try the Google Docs integration on n8nSee the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Google Docs n8n integration do?

The Google Docs node lets a workflow create, read, and update documents without anyone opening the Google Docs editor. It ships with every n8n install under the name n8n-nodes-base.googleDocs and runs on a credential, the connection you save once in the n8n Credentials menu and reuse everywhere, here a Google OAuth2 or Service Account one.

One resource, Document, 3 operations: create a document from a title, get its content, update its text. No trigger comes with it, so nothing on the Google Docs side ever starts a workflow by itself.

A project closes, and the workflow does the writing: it pulls the epic summary out of Jira, has an AI agent draft the lessons-learned report, calls Create a document to open a new Google Doc, then Update a document to pour the text in. A message in Slack tells the team it is ready. Nobody pastes anything.

A support bot works the other way around. Get a document reads the shared FAQ doc on a schedule, the text becomes context for an AI agent, and the answer goes back out through Slack or WhatsApp. The doc stays the one file the team still edits by hand.

Third case, a knowledge base: a Drive trigger spots each new file, Get a document returns its text, the workflow chunks it and stores it for a chatbot to search later. The docs stay where the writers already work, and the bot answers from them.

Create, get, update, and that is the whole node. No formatting beyond what Actions allows, no images, no comments, no delete. That is where the HTTP Request node comes in: it calls the Google Docs API directly and reuses the same OAuth2 or Service Account credential, so the node changes and the connection does not.

No trigger, then: nothing in n8n watches a Google Doc for edits. The workflow has to start somewhere else, with a Schedule Trigger that checks back on a fixed interval, a Webhook (a URL n8n exposes for another service to call), or the trigger of an app already wired in, such as Google Sheets or Gmail.

If n8n is still new to you, the n8n training covers the basics before this node goes into a workflow that runs for real, and the n8n review says where the tool is strong.

Connect

How do you connect Google Docs to n8n?

  1. 01

    Sign in with Google on n8n Cloud

    On n8n Cloud, open the Google Docs credential and click Sign in with Google. Google Docs is one of the nodes covered by Managed OAuth2, so n8n runs the whole OAuth exchange in the browser and there is nothing to create in the Google Cloud Console. A self-hosted instance never shows that button, and the dropdown on the same screen switches the credential to Custom OAuth2, which the next two steps set up.

  2. 02

    Create the Google Cloud OAuth client

    In the Google Cloud Console, create a project, enable the Google Docs API, then fill the OAuth consent screen with an App name and a User support email. Add n8n.cloud or your own domain under authorized domains, and create an OAuth client of type Web application: Google hands back the Client ID and Client Secret the n8n credential asks for.

  3. 03

    Paste the redirect URL and save

    Copy the OAuth Redirect URL from the n8n credential screen and paste it into Authorized redirect URIs on the Google side. Running n8n on your own machine needs no public domain and no SSL certificate: Google accepts localhost, so the URL reads http://localhost:5678/rest/oauth2-credential/callback. Save both sides, and the node lists the credential in its dropdown.

Actions

What can the Google Docs node do?

The Google Docs node exposes 3 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetUpdate
Document✓✓✓

Document

3 operations
01

Create a document

document.create

What you see in n8n

Notes & use cases

Creates an empty Google Doc in the Drive folder you point at, ready for the rest of the workflow to write into.

Key parameters

  • Drive Name or ID: the Drive that holds the file, picked from the dropdown, or its ID passed with an expression, the {{ $json.field }} syntax that reads a value off the incoming item.
  • Folder Name or ID: the destination folder. Same dropdown, and the same expression when every run files its doc somewhere else.
  • Title: the only text this operation writes. The document comes out empty, so an Update a document call always follows.
Use cases
one monthly report per client, filed in that client's Drive folder with the date already in the title.
02

Get a document

document.get

What you see in n8n

Notes & use cases

Reads an existing Google Doc and returns its content as a single item, the unit n8n passes from one node to the next.

Key parameters

  • Doc ID or URL: paste the whole browser URL and n8n takes the ID out of it, which helps when a colleague simply sends you the link.
  • Simplify: leave it on while the text feeds an AI agent, a summary or a Slack message. Turn it off when the workflow needs Google's raw response instead.
Use cases
re-reading the shared FAQ doc before each support reply, so the answer quotes the version the team fixed yesterday.
03

Update a document

document.update

What you see in n8n

Notes & use cases

Applies a list of edits to a document that already exists, text inserts included, in the order the list puts them.

Key parameters

  • Doc ID or URL: the document to edit. It has to exist already, so the value comes from the step that created it or from a URL you kept.
  • Actions: one Add Action per edit. This is where the whole effect of the operation sits.
  • Update Fields and Simplify: both optional. A plain text insert needs neither, and Simplify only trims the response sent back.
Use cases
adding the week's release notes to a tracking doc that lives all year, rather than starting a new one every time.
Need help

Need help automating Google Docs with n8n?

A person reads every message.

FAQ

Google Docs and n8n: frequently asked questions

01Is the Google Docs n8n integration free?
Yes. The Google Docs node ships with every n8n install, on n8n Cloud and on a self-hosted instance running the Community Edition under the Sustainable Use License, at no extra cost on the n8n side. Nothing to install either: the node already sits in the list when you add a step. What Google charges for a Docs or Workspace account is a separate question, and it changes nothing about the node. Once a Google OAuth2 or Service Account credential is saved, the node runs in as many workflows as needed, the same way on Cloud or self-hosted n8n.
02What credentials or rights does it need?
Two methods work. OAuth2 is the recommended one: on n8n Cloud, Managed OAuth2 signs in with a single click; self-hosted n8n needs a Custom OAuth2 app created in the Google Cloud Console with a Client ID and Client Secret. Service Account is the alternative, meant for the handful of Google nodes that support it: it needs a JSON key downloaded from the Cloud Console, then its client_email and private_key pasted into the n8n credential. OAuth2 covers most setups; Service Account suits automated, no-login scenarios.
03What are the limits of the Google Docs node?
It only creates, reads, and updates a document: it cannot format text beyond what the Actions collection covers, insert images, manage comments, or delete a file. There is no list or search operation either, so a workflow needs the document's ID or URL from somewhere else, another node or an earlier step. For anything the node does not expose, the HTTP Request node reaches the Google Docs API directly and reuses the same OAuth2 or Service Account credential, so the missing operation costs one extra node, not a new connection.
04Does the Google Docs node react in real time?
No, because it has no trigger at all: nothing in n8n watches a Google Doc for edits by itself. A workflow that should react to a document has to start somewhere else, a Schedule Trigger that checks on a fixed interval, a Webhook that a connected service calls, or the trigger of another app already in the workflow. Google Docs then only appears further down the workflow, through Create a document, Get a document, or Update a document, once something else has kicked things off.
05n8n or Make for Google Docs?
It depends on where the workflow already lives. n8n self-hosts on Docker or npm, or runs on n8n Cloud, n8n's own hosted offering, with the same workflow either way and full control over where the data sits. Make (formerly Integromat) only runs hosted, with no self-hosting option, and bills per operation rather than per workflow run. Teams that need to keep data on their own servers, or that already build visual workflows in n8n, get more from the native node; the choice mostly comes down to hosting and cost model, not the Google Docs node itself.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations