Resources · Make integration

Google Docs Make integrationAutomate Google Docs with Make.

What if your contracts, quotes and reports wrote themselves from a template? The Google Docs Make integration gives you 13 modules: 1 trigger, 11 actions and 1 search. This guide is for ops and sales teams who fill the same documents by hand, and it walks you from the connection to a working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Google Docs Make integration do for you?

The Google Docs Make integration links your Google account to Make, a visual tool where you chain apps without writing code. Inside Make, you build a scenario (the automation itself, a chain of modules) that can create documents, fill templates, edit text, add images or download files, all from data that comes from your other apps.

Documents that fill themselves. A deal is signed in your CRM, and Create a Document from a Template copies your contract model and swaps each tag for the client's name, address or amount. Nobody pastes anything, and every copy follows the same layout.

Files your other tools can use. Once a document is ready, Download a Document hands a file to the next module, which can attach it to an email or drop it into storage. Add Make All Links in a Document Clickable before that step when your text contains raw web addresses.

A folder that reports its changes. Watch Documents looks at one folder and passes along every document created or modified there, so Get Content of a Document can read the text and push it to a spreadsheet, a chat or a task tool.

Two limits are worth knowing. Watch Documents is scheduled, so it catches changes at the pace of the scenario, not the second they happen. And anything Make receives from Google APIs follows the Google API Services User Data Policy. If you work in n8n too, the Google Docs n8n integration covers the same app, and n8n vs Make lays the two tools side by side. To see what each plan includes, read Make pricing.

Connect

How do you connect Google Docs to Make?

  1. 01

    Add a Google Docs module

    You need a Google account, nothing more. In your Make scenario, add any Google Docs module and click Create a connection. A connection is your Google account linked to Make once; every Google Docs module reuses it afterward.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear label (the account owner, or work versus personal) saves you from guessing later when several Google accounts sit in the same Make organization.

  3. 03

    Sign in and grant access

    Click Sign in with Google, pick the account, and accept every permission Google asks for, then confirm. Once that is done, Make can list your folders and files.

First scenario

Build your first scenario: a filled contract, ready to send

GoalWhen a new client record arrives from another app, Make fills your Google Docs template and downloads the finished document.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the module of the app that holds your client data, such as a form or a CRM, and connect it.

  2. 02

    Add the template module

    Click the + to the right of that first module, search for Google Docs and choose Create a Document from a Template. Create your connection if it does not exist yet.

  3. 03

    Map the client data

    Select your template document, then give each tag a value mapped from the first module, like the client name or the signed amount. Make lists the data it received.

  4. 04

    Download the new document

    Add Download a Document after the template module and point it at the document just created. The file it outputs can then feed an email or storage module further down the chain.

  5. 05

    Test with Run once

    Click Run once and let a real record come through. Open the bundles, meaning the items each module received and passed on, to check that every tag was replaced.

  6. 06

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then turn the scenario on. From now on, each new record produces its own document.

Triggers

What starts a Google Docs scenario

1 module starts a scenario when something happens in Google Docs. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Google Docs as soon as it happens.

Google Docs1Watch Documents

Watch Documents

Scheduled trigger

In MakeTriggers when a new document is created or modified in a specific folder.

Watch Documents keeps an eye on one folder and starts your scenario with every document that is new or has been edited there. Each document arrives as its own bundle, ready for the next module.

How it fires
scheduled, so Make checks the app on the scenario's schedule (every 15 minutes by default, never below 15 on the Free plan).
When to use it
a shared folder where colleagues write meeting notes or briefs that you want copied into a tracker once they exist.
Watch out
it also picks up modified documents, which suggests that a scenario editing files in that same folder would pick up its own edits. Keep outputs in another folder.
Modules

Every Google Docs module, and when to pick it

Google Docs gives you 12 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Document

10 modules
Google Docs1

List Documents

Search

In MakeRetrieves a list of documents.

This search returns the documents Make finds, one bundle per document, so you can loop over a whole set in a single run.

When to use it
you want to process documents that already exist, such as every brief in a folder, rather than waiting for changes.
Watch out
a search can return zero, one or many results, and each result costs its own operations further down.
Google Docs2

Get Content of a Document

Action

In MakeGets a content of a document.

Reads a document and hands its content to the rest of the scenario, so text written in Google Docs can travel to a sheet, a CRM note or a chat message.

When to use it
right after Watch Documents, when the trigger tells you which file changed but you need what is written inside.
Google Docs3

Create a Document

Action

In MakeCreates a new Google document by adding the content of HTML format.

Produces a brand new Google document from content you supply in HTML format, so headings, bold text and paragraphs can be described with tags.

When to use it
the layout changes from one run to the next, for instance a summary assembled from form answers, so a fixed template would not fit.
Watch out
the module expects HTML, so if your source only gives plain text, format it before this step.
Google Docs4

Create a Document from a Template

Action

In MakeCreates a copy of an existing template document and replaces any tags e.g. {{!notfound:name}}, {{!notfound:email}}. This module also allows users to replace images by new images with URLs.

Copies a template you prepared and replaces its tags with real values, and it can also swap template images for new ones taken from a URL. The original stays untouched.

When to use it
contracts, quotes, offer letters and certificates where only names, dates and amounts change.
Watch out
check that each tag in the template matches the one you map; a Run once on a test record shows any tag left unreplaced.
Google Docs5

Insert a Paragraph to a Document

Action

In MakeInserts or appends a new paragraph to an existing document.

Adds a new paragraph to a document that already exists, so one file can grow over time instead of multiplying into dozens of small ones.

When to use it
a running log or journal, where each new support ticket or order adds one line of text to the same shared document.
Watch out
an insertion modifies the file, so if Watch Documents monitors its folder, expect it to pick that document up again.
Google Docs6

Insert an Image to a Document

Action

In MakeInserts a new image with URL to a document. The original size of the image is entered or the image is resized as required by the user. The original image ratio is maintained.

Places an image taken from a URL into a document. You keep its original size or set a new one, and the proportions stay intact either way, so logos and photos never look stretched.

When to use it
a product sheet or report that needs a picture supplied by another app, such as a chart or a product photo.
Google Docs7

Replace an Image with a New Image

Action

In MakeReplaces an existing image with a new image with URL in the document. In order to fill the original image's bounds, the new image may be scaled or cropped.

Swaps an image already in the document for another one from a URL, which keeps your layout and replaces only the picture.

When to use it
a recurring document where the chart or the product shot changes but the page design stays the same.
Watch out
the new image fills the old one's frame, so Make may scale or crop it; pick images with a similar shape.
Google Docs8

Replace a Text in a Document

Action

In MakeReplaces an old text by a new text in a document.

Finds an old piece of text in a document and puts new text in its place, handy when the file already exists and you do not want a fresh copy.

When to use it
updating a status, a price or a name in a live document shared with a client or a team.
Watch out
choose a distinctive search text, or you may change more words than you meant.
Google Docs9

Download a Document

Action

In MakeDownloads a document to a required format.

Turns a Google document into a downloadable file in the format you choose, so apps that cannot open Google Docs still receive something usable.

When to use it
after a template is filled, to attach the finished file to an email or send it to cloud storage.
Watch out
on the Free plan, Make handles files up to 5 MB.
Google Docs10

Delete a Document

Action

In MakeDeletes a document.

Deletes the document you point it to, which keeps working folders tidy once a file has done its job and nobody needs it anymore.

When to use it
temporary drafts created only to be downloaded, once the downloaded file sits safely elsewhere.
Watch out
test with Run once on a throwaway document first, because the wrong mapping deletes the wrong file.

Other

2 modules
Google Docs11

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Calls any endpoint of the Google Docs API with the connection you already set up, which covers whatever the ready-made modules leave out.

When to use it
you need an operation no other module on this page offers and you are comfortable reading the API documentation.
Watch out
you write the request yourself, so keep the Google Docs API documentation open while you build it.
Need help

Need help automating Google Docs with Make?

A person reads every message.

FAQ

Google Docs and Make: common questions

01Is the Google Docs Make integration free?
Yes. Google Docs is a standard app, so it works from the Free plan onward. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in operations per month. Your Google account itself is enough on the Google side.
02What do you need to connect Google Docs to Make?
A Google account. You add a Google Docs module, click Create a connection, optionally give it a name, then click Sign in with Google and accept every permission requested. Advanced users can instead paste the client ID and secret of their own Google Cloud project, which then needs the Google Docs API and Google Drive API enabled and an OAuth consent screen set up. Most people never need that path and use the standard sign-in.
03Does the Google Docs trigger in Make react in real time?
No. Watch Documents is a scheduled trigger: Make checks your folder on the scenario's schedule and picks up documents created or modified since the last check. A new scenario checks every 15 minutes by default. On the Free plan you cannot go below 15 minutes, while paid plans allow intervals down to 1 minute. If you need a document created the moment something happens elsewhere, start the scenario from the other app's trigger and use Google Docs only for the actions.
04What if a Google Docs module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Google Docs API with the same connection, so an operation missing from the 12 other modules can still run in your scenario. You build the request yourself, which takes some comfort with API documentation. Also keep in mind that data Make receives from Google APIs follows the Google API Services User Data Policy, which frames how it can be shared with other apps.
05Should you use Make or n8n for Google Docs?
It depends on the tool your team already uses. Google Docs has a Make app with 13 modules, and n8n offers a node for the same app, and this page does not compare them module by module here. The practical criterion is where the rest of your automations live: keeping one tool means one place to manage connections and follow runs. The comparison page linked above sets out the differences between the two tools in more detail.