Resources · Make integration

Google Tasks Make integrationAutomate Google Tasks with Make.

What if new to-dos landed in Google Tasks without anyone typing them? The Google Tasks Make integration gives you 13 modules: 2 scheduled triggers, 9 actions and 2 searches. This guide shows you how to link your account and build a first working scenario.

Try the Google Tasks integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Google Tasks Make integration do for you?

The Google Tasks Make integration lets Make read, create, update and delete your tasks and task lists for you. You build a scenario (the automation itself, a chain of modules) and each module (one brick: a trigger, an action or a search) handles one step, with no code to write.

A to-do for every request that comes in. When a deal moves in your CRM or a form is submitted, Create a Task writes the follow-up into the right list. The salesperson opens Google Tasks and the next step is already there.

A checklist that follows your projects. Watch Task Lists notices when a list is created or updated, so a new project list can kick off the rest of the process, and Create a Task List does the reverse when a project starts somewhere else.

A tidy-up without clicking through every item. List Tasks pulls every task of a list, then Update a Task or Delete a Task acts on each one.

What Make does not do here: neither trigger is instant, so Make checks Google Tasks on the scenario's schedule rather than hearing about changes the moment they happen. For anything the 13 modules skip, Make an API Call reaches the rest of the Google Tasks API. The same app also has a node on the other side, described on the Google Tasks n8n integration page, and the n8n vs Make comparison helps you pick a tool. Still new to the editor? The Make training walks through the basics.

Connect

How do you connect Google Tasks to Make?

  1. 01

    Turn on the Google Tasks API

    You need a Google account first. In the Google Cloud Console, enable the Google Tasks API for your project. Without this switch, Make has no way to talk to your tasks, even with a valid Google login.

  2. 02

    Add a module and create the connection

    In your scenario, add any Google Tasks module and click Create a connection. A connection is your Google account linked to Make once, then reused by every Google Tasks module. You can type a label in Connection name if you like.

  3. 03

    Sign in or paste your own credentials

    Follow the on-screen instructions to authorize Make. If you prefer your own OAuth client, create it in Google Auth platform under Clients, choose Desktop app, then paste the Client ID and Client secret into Make.

First scenario

Your first scenario: turn a new request into a Google task

GoalWhen a new item shows up in another app, Make creates a matching task in Google Tasks.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where requests arrive, such as a form tool or a spreadsheet.

  2. 02

    Set up the starting module

    Connect that app and fill its fields. Once the connection exists, Make lists what it can read, so you choose the form or sheet from a menu instead of typing it.

  3. 03

    Add Create a Task

    Click the + on the right of the first module, search for Google Tasks and pick Create a Task. Create the Google connection, then choose the task list that should receive the to-dos.

  4. 04

    Map the request into the task

    Fill the task fields with data from the first module, such as the subject of the request. Each bundle (one item passing from module to module) becomes one task.

  5. 05

    Test with Run once

    Add a test request in the source app, then click Run once. Open each module's bubble to read the bundles it received and check that the task appeared in Google Tasks.

  6. 06

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval.

Triggers

What can start a Google Tasks scenario?

2 modules start a scenario when something happens in Google Tasks. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Google Tasks as soon as it happens.

Google Tasks1Watch Task Lists

Watch Task Lists

Scheduled trigger

In Make“Triggers when a task list is created and updated.”

Watch Task Lists starts your scenario whenever a task list is created or updated in your Google account, and passes that list along as a bundle for the next modules to use.

How it fires
scheduled. Make checks Google Tasks on the scenario's schedule, every 15 minutes by default, so a new list shows up on the next check rather than the instant it appears.
When to use it
when creating a list is itself the signal, for instance a new list per client or per project that should also open a folder or a channel elsewhere.
Watch out
it looks at lists, not at the tasks inside them. To react to individual to-dos, pick Watch Tasks.
Google Tasks2Watch Tasks

Watch Tasks

Scheduled trigger

In Make“Triggers when a new event occurs in a specified task list.”

Watch Tasks keeps an eye on one task list you choose and launches the scenario when a new event occurs there, handing each new item to the following modules.

How it fires
scheduled. Make checks the list on the scenario's schedule, so new items reach the scenario at the next check. On the Free plan the gap between checks is 15 minutes at the shortest; paid plans go down to 1 minute.
When to use it
a shared list where a manager adds work, and you want those items copied into your team's tracker or announced in chat.
Watch out
it follows the one list selected in the module, so tasks added to your other lists stay outside the scenario unless you watch them too.
Modules

Every Google Tasks module in Make

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

Google Tasks1

Create a Task

Action

In Make“Creates a new task.”

Create a Task adds a new to-do to the list of your choice, filled with whatever the previous modules send it. This is the module most scenarios end on.

When to use it
a support ticket, a signed quote or a form reply that should turn into a follow-up nobody forgets.
Watch out
every bundle it receives produces one task, so a search placed before it can create many tasks in a single run.
Google Tasks2

Create a Task List

Action

In Make“Creates a new task list.”

Create a Task List opens a brand new list in Google Tasks, ready to receive tasks from the modules that follow in the same scenario.

When to use it
a project or a client onboarding starts in another tool and deserves its own checklist, which you then fill with Create a Task.
Watch out
run it only once per project; putting it on a trigger that fires on every change would pile up duplicate lists.
Google Tasks3

Delete a Task

Action

In Make“Deletes a task.”

Delete a Task removes one task from a list, which keeps Google Tasks clean when the work behind it disappears somewhere else.

When to use it
an order is cancelled or a meeting is dropped, and the matching to-do should go with it.
Watch out
treat the deletion as final. Test with Run once on a dummy task first and check which task the module points to before switching the scenario on.
Google Tasks4

Delete a Task List

Action

In Make“Deletes a task list.”

Delete a Task List gets rid of a whole list in one step, which is cleaner than removing its tasks one by one with Delete a Task.

When to use it
a project closes in your management tool and its checklist no longer has a reason to stay in Google Tasks.
Watch out
this is the widest delete of the app. Map the list carefully and keep a filter in front of it so only closed projects reach it.
Google Tasks5

Get a Task

Action

In Make“Returns the data of a specified task.”

Get a Task fetches the full data of one specific task, so later modules work with its current version instead of a stale copy.

When to use it
another app stores a reference to a task, and you need the latest version before writing a report or sending a reminder.
Watch out
it reads one task you designate. To browse a whole list, List Tasks is the right choice.
Google Tasks6

Get a Task List

Action

In Make“Returns the data of a specified task list.”

Get a Task List returns the details of one list you point it to, handy when a scenario only knows which list is concerned and needs its data.

When to use it
after Watch Tasks, to add the list's name to a chat message so readers know which project the new item belongs to.
Watch out
it describes the list, not its content. The tasks themselves come from List Tasks.
Google Tasks7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you send your own request to the Google Tasks API with the connection you already set up, covering anything the other 12 modules leave out.

When to use it
you need an operation of the Google Tasks API that has no dedicated module, and you know which endpoint to call.
Watch out
you build the request yourself, so read the Google Tasks API reference first and test the call with Run once before relying on it.
Google Tasks8

Update a Task

Action

In Make“Updates an existing task.”

Update a Task changes an existing to-do in place, so Google Tasks reflects what happened elsewhere without anyone editing it by hand.

When to use it
a deal changes stage in the CRM and the related follow-up should reflect the new stage.
Watch out
avoid starting the scenario with Watch Tasks on the same list you update: the edited task can be picked up again at the next check and start a loop.
Google Tasks9

Update a Task List

Action

In Make“Updates an existing task list.”

Update a Task List edits an existing list, which keeps its name in line with the project or client it belongs to.

When to use it
a client renames their company or a project gets a new code, and the list in Google Tasks should follow.
Watch out
Watch Task Lists also reacts to updated lists, so pairing both on the same account can retrigger your own scenario.
Google Tasks10

List Task Lists

Search

In Make“Returns a list of all task lists.”

List Task Lists returns every list of the connected account, each as its own bundle, giving you a full inventory to loop over.

When to use it
an overview of all your lists sent to a spreadsheet, or a scenario that must look for a list by name before deciding whether to create it.
Watch out
each list that comes out runs the next modules once, and every module run counts as an operation (the unit Make counts on your plan).
Google Tasks11

List Tasks

Search

In Make“Returns a list of all tasks in the specified task list.”

List Tasks pulls all the tasks of the list you pick, one bundle per task, so you can filter them, copy them or act on each one in the same scenario.

When to use it
exporting a list to a spreadsheet, or checking every open item of a project before its review.
Watch out
a long list means many bundles and many operations downstream; add a filter right after it to keep only what matters.
Need help

Need help automating Google Tasks with Make?

A person reads every message.

FAQ

Google Tasks and Make: common questions

01Is the Google Tasks Make integration free?
Yes. Google Tasks is a standard app, so it is available on Make's Free plan. That plan comes with limits: 2 active scenarios, 15 minutes at least 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 and remove the cap on active scenarios. Make counts usage in credits, one operation per module run on each bundle.
02What do you need to connect Google Tasks to Make?
A Google account with the Google Tasks API enabled in the Google Cloud Console. Then you add a Google Tasks module, click Create a connection and follow the authorization steps. If you want your own OAuth client, create it in Google Auth platform under Clients with the Desktop app type, add the callback URI if Google asks for one, and paste the Client ID and Client secret into Make. One connection then serves all 13 modules.
03Does the Google Tasks trigger in Make react instantly?
No. Both triggers, Watch Tasks and Watch Task Lists, are scheduled: Make checks Google Tasks at the interval set on the first module, every 15 minutes by default. On the Free plan, 15 minutes is also the minimum, while paid plans allow 1 minute. A change made in Google Tasks therefore reaches your scenario at the next check. There is no instant trigger with a webhook for this app in Make.
04What if the Google Tasks module you need is missing in Make?
Use Make an API Call. It sends any request to the Google Tasks API with the connection you already have, so an endpoint without its own module stays reachable. You write the request yourself, which calls for a look at the Google Tasks API reference and a test with Run once. The Make documentation for this app also warns that its content is AI-generated from Google's docs, so verify key details with Google.
05Should you use Make or n8n for Google Tasks?
It depends on the tool your team already works in. In Make, Google Tasks offers 13 modules: 2 scheduled triggers, 9 actions including Make an API Call, and 2 searches, and it runs on the Free plan. n8n also has a Google Tasks node, with its own page on this site. Compare the modules each side offers for your exact use case, then read the n8n vs Make comparison in the resources before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations