Resources · Make integration

Google Keep Make integrationAutomate Google Keep with Make.

What if your notes wrote, shared and tidied themselves? The Google Keep Make integration gives you 8 modules: 1 scheduled trigger, 6 actions and 1 search. This guide is for anyone who lives in Keep, and it walks you from the connection to a first working scenario.

Try the Google Keep integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Google Keep Make integration let you automate?

The Google Keep Make integration links your Keep account to Make so notes can be created, read, shared and deleted by a scenario, which is the automation you build in Make: a chain of modules, each one a single brick such as a trigger, an action or a search. You set it up once and it runs without you.

Notes that appear on their own. Put Create a Note after a module from another app, such as a form or a mail app, and every new entry lands in Keep as a note you can read on your phone. Handy for a sales rep who wants each inbound lead written down where they already look.

Access that follows the project. Create a Permission gives a teammate writer access to a note, and Delete a Permission takes it back, so an operations lead can open and close shared checklists as people join or leave a project.

A clean archive elsewhere. Watch Notes spots notes that were created or updated, and List Notes or Get a Note pull their content, ready to be copied into a table. If your team keeps its records in a base, the Airtable Make integration is a natural next stop.

What the listed modules do not cover, Make an API Call can reach, with the same connection. The same app may also exist on n8n; the n8n vs Make comparison lays out how the two tools differ, and the Make training goes deeper once this page is done.

Connect

How do you connect Google Keep to Make?

  1. 01

    Prepare your Google credentials

    You need a Google account with access to Keep. In the Google Cloud console, open Menu, then Google Auth platform, then Clients, click Create Client, choose the application type, name it and click Create.

  2. 02

    Copy the Client ID and secret

    Google now shows the Client ID and the Client secret. Copy both somewhere safe for a moment: Make asks for them in the next step, and they are what lets Make act on your Keep account.

  3. 03

    Create the connection in Make

    Add any Google Keep module to your scenario and click Create a connection. Give it a name in Connection name if you like, paste your credentials or follow the on-screen prompts. Every Keep module then reuses this connection.

First scenario

Your first scenario with Google Keep

GoalWhen a new entry arrives in another app, Make writes it into Google Keep as a fresh note.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your entries start, such as a form tool, and its module that watches for new entries.

  2. 02

    Add Create a Note

    Click the + on the right of that first module, search for Google Keep and choose Create a Note. Select the connection you made earlier, or click Create a connection now.

  3. 03

    Map the entry into the note

    Fill the fields of Create a Note by clicking into them and picking data from the first module. Each bundle, meaning one item passed from a module to the next, becomes one note.

  4. 04

    Test with Run once

    Click Run once, then add a test entry in the source app. Open the bubble above each module to read the bundles it received, and check Keep for the new note.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set Scheduling. A new scenario checks every 15 minutes by default. Pick what suits you, then switch the scenario on.

Triggers

What can start a Google Keep scenario?

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

Google Keep1Watch Notes

Watch Notes

Scheduled trigger

In Make“Triggers when a note is created or updated.”

Watch Notes hands your scenario every Keep note that was just created or edited, so a change you make on your phone can travel to the rest of your tools without a copy and paste.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and at least 15 minutes apart on the Free plan.
When to use it
you want each edited meeting note mirrored into a shared table or sent to a colleague.
Watch out
an update counts too, so if a later module of the same scenario edits that note, it can be picked up again on the next check.
Modules

What can Make do in Google Keep?

Google Keep gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Google Keep1

Create a Note

Action

In Make“Creates a new note.”

You get a brand new note in Keep, filled from whatever the earlier modules passed along, so ideas and requests captured elsewhere end up in the app you open all day.

When to use it
a lead form, an email or a calendar entry should leave a written trace in Keep.
Watch out
each bundle creates one note, so a search placed before it can produce many notes in one run.
Google Keep2

Create a Permission

Action

In Make“Creates one or more permissions on the note. Only permissions with the WRITER role may be created. If adding any permission fails, then the entire request fails and no changes are made.”

This module opens a note to other people, so a teammate can edit the same checklist instead of waiting for a screenshot.

When to use it
someone joins a project and should work on its shared notes right away.
Watch out
only the WRITER role can be granted, and if a single permission in the request fails, none of them is added.
Google Keep3

Delete a Note

Action

In Make“Deletes a note.”

The result is a lighter Keep: a note that has served its purpose disappears without you hunting for it by hand.

When to use it
after the note's content has been copied somewhere more durable, such as a table or a task manager.
Watch out
treat the deletion as final: run the scenario on a throwaway note first, and keep this module at the very end of the flow.
Google Keep4

Delete a Permission

Action

In Make“Deletes one or more permissions on the note. The specified entities will immediately lose access. Permission with the OWNER role can't be removed.”

Here you take access away: the people you name lose the note at once, which keeps shared lists limited to those still on the job.

When to use it
a contractor leaves, or a project closes and its notes should go back to private.
Watch out
the OWNER cannot be removed, so this module only ever trims the people the owner invited.
Google Keep5

Get a Note

Action

In Make“Returns a note.”

You receive the full content of one specific note, ready to be mapped into the next module of the scenario.

When to use it
you already know which note you need, for example the one Watch Notes just flagged, and you want its details.
Watch out
it reads a single note; to go through several, List Notes is the better choice.
Google Keep6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this module you reach any endpoint of the Google Keep API through the connection you already set up, so a need the other modules miss does not stop the project.

When to use it
the action you want has no dedicated module in the list above.
Watch out
you write the request yourself, so keep the API documentation open while you fill it in.
Google Keep7

List Notes

Search

In Make“Lists notes.”

This search brings back your notes as separate bundles, so the modules after it can handle them one by one, which suits a bulk export or a cleanup.

When to use it
you want to copy a whole set of notes into a table before reorganizing your Keep.
Watch out
a search can return zero, one or many bundles, and every module after it counts operations for each one.
Need help

Need help automating Google Keep with Make?

A person reads every message.

FAQ

Google Keep and Make: common questions

01Is the Google Keep Make integration free?
Yes, Google Keep is a standard app, so it works on the Free plan of Make. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits, meaning operations, per month. An operation is one module running on one bundle.
02What do you need to connect Google Keep to Make?
You need an active Google account with access to Google Keep and your own OAuth credentials. In the Google Cloud console you create a client under Google Auth platform, then copy the Client ID and Client secret it shows. If Google asks for a callback URI, use the one given in the Make documentation for Google Keep. In Make you then click Create a connection on any Keep module and paste those details, and every other Keep module reuses that connection.
03Does the Watch Notes trigger react in real time?
No. Watch Notes is a scheduled trigger: Make checks Google Keep on the scenario's schedule rather than being alerted by Keep. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, while paid plans can go down to 1 minute. You can also click Run once whenever you want to pick up changes immediately while you are testing the scenario.
04What if a Google Keep module is missing in Make?
Use Make an API Call. This module calls any endpoint of the Google Keep API with the connection you already created, so you are not limited to the 8 modules listed on this page. You write the request yourself, which takes a look at the API documentation. Also note that the Make documentation for this app carries a warning that it was generated with AI, so check any detail that matters directly with Google.
05Google Keep: Make or n8n?
It depends on the tool your team already uses, since the choice rests on criteria rather than on this one app. On the Make side, this page shows what you get: 8 modules, one scheduled trigger and an API call module for the rest. Google Keep may also have a node on n8n. The n8n vs Make comparison on this site sets the two tools side by side, without ranking them, so you can decide with your own requirements in hand.
Same platform

Other docs you might need on this stack.

Browse all integrations