Resources · n8n integration

Google Tasks n8n integrationAutomate Google Tasks with n8n.

A checklist only helps when something else keeps it up to date. The Google Tasks n8n integration exposes one resource, Task, with 5 operations: create, get, get many, update, delete. There is no Google Tasks trigger node, so the workflow starts somewhere else and the tasks follow.

Try the Google Tasks integration on n8nSee the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Google Tasks n8n integration actually cover?

The Google Tasks node calls the Google Tasks API from inside an n8n workflow. It works on a single object, the task, inside a task list you pick from a dropdown that n8n loads from your account. The 5 operations cover the whole life of that task: created, read, listed in bulk, updated, removed. All of it runs under one Google credential, meaning the stored authorization n8n uses to call the API on your behalf.

First scenario: the inbox stops being a to-do list. An email tagged by a rule in Gmail reaches the workflow, task.create writes a task titled after the subject line, and Due Date puts it on a day rather than in a pile. The sender address goes into Notes, so whoever opens the task knows who is waiting.

Second scenario: a morning digest. A Schedule Trigger, the n8n node that fires on a fixed interval, runs task.getAll with Due Max set to today, and posts what comes back to a channel in Slack. The same list can be appended to Google Sheets when someone wants a record of what was open each day.

Third scenario: closing the loop from the tool where the work really happens. A card moved to done in ClickUp feeds task.update with Status on completed, so nobody ticks the same thing twice. The Task ID travels through the workflow as an expression, the n8n syntax for reading a field of the incoming item.

Where the node stops: it handles tasks, not the lists themselves. Creating a task list, renaming one or enumerating the lists of an account are not operations here. For those calls, the HTTP Request node reaches any Google Tasks API endpoint and reuses the same credential through predefined authentication, so nothing extra is set up.

Two other limits are worth knowing before building. Google Tasks has no trigger node in n8n, so nothing pushes a change to you: a workflow reacts on a schedule, on an n8n Webhook called by another service, or on another tool's trigger. And on task.getAll, Return All left off means n8n stops at Limit, which is a good way to think a list is shorter than it is. The n8n review goes further into what the platform does well and where it gets tedious.

Connect

How do you connect Google Tasks to n8n?

  1. 01

    Create the credential in n8n

    Open the Credentials menu in n8n and create a Google credential for Google Tasks. A credential is the stored authorization, created once and offered in the dropdown of every node that needs it. On n8n Cloud, the fastest route is Managed OAuth2: click Sign in with Google on the credential screen and nothing else is needed in the Google Cloud Console.

  2. 02

    Set up a custom OAuth2 app for self-hosted n8n

    Managed OAuth2 is not available on a self-hosted instance, so create the app yourself. In the Google Cloud Console, create a project, enable the APIs you need, then go to APIs & Services > OAuth consent screen and fill in App name and User support email. For Audience, Internal covers users of your own Google Workspace, External covers any Google account. Under Branding, add n8n.cloud as an authorized domain, or the domain of your instance.

  3. 03

    Match the redirect URL and paste the keys

    Still in the console, go to Credentials, select + Create credentials > OAuth client ID and pick Web application as the application type. Copy the OAuth Redirect URL shown in your n8n credential into Authorized redirect URIs. Running n8n locally works too, since Google accepts localhost, for example http://localhost:5678/rest/oauth2-credential/callback. Create the client, then paste the Client ID and Client Secret back into n8n.

Actions

The 5 operations of the Google Tasks node

The Google Tasks node exposes 5 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
ResourceCreateGetGet ManyUpdateDelete
Task✓✓✓✓✓

Task

5 operations
01

Create a task

task.create

What you see in n8n

Notes & use cases

Adds a task to the list you choose and returns the created task, identifier included, which the rest of the workflow can reuse.

Key parameters

  • TaskList Name or ID: the list the task lands in, picked from the dropdown or set with an expression when the list depends on the incoming data.
  • Title: the text read in Google Tasks, often built from the item, for example {{ $json.subject }}.
  • Additional Fields: where the useful part sits, with Due Date, Notes for context, Status (needsAction or completed) and Parent to nest the task under another one.
Use cases
a signed quote creates the onboarding task, due in 2 days, with the client reference in Notes.
02

Delete a task

task.delete

What you see in n8n

Notes & use cases

Removes one task from a list for good. Nothing comes back to undo it, so the branch that leads here deserves a condition above it.

Key parameters

  • TaskList Name or ID: required even for a delete, because a task identifier only makes sense inside its own list.
  • Task ID: the identifier returned by Google, not the title. It usually arrives as {{ $json.id }} from a previous node.
Use cases
a meeting cancelled in Google Calendar clears the prep task that was created with it, instead of leaving a task about something that will not happen.
03

Get a task

task.get

What you see in n8n

Notes & use cases

Reads a single known task and returns its current fields, which is how a workflow checks the state of something before acting on it.

Key parameters

  • TaskList Name or ID: the list holding the task.
  • Task ID: the exact identifier. Store it when the task is created, otherwise a get many is needed first to find it again.
Use cases
before sending a reminder, the workflow reads the task and stops when its status already shows completed, which keeps the nudge from landing on finished work.
04

Get many tasks

task.getAll

What you see in n8n

Notes & use cases

Pulls the tasks of one list, with filters that decide what counts as relevant today.

Key parameters

  • Return All: on, n8n walks the API pages and brings every task back. Off, it stops at Limit, which is fine for a preview and misleading for a report.
  • Additional Fields: Due Min and Due Max bound the due date as RFC 3339 timestamps, Updated Min catches what moved recently, and Show Completed only shows tasks finished in Google's own apps when Show Hidden is true as well.
Use cases
a Monday digest of everything due this week, sent to the person who owns the list.
05

Update a task

task.update

What you see in n8n

Notes & use cases

Changes an existing task without touching the fields left empty, which is what makes it safe to run on a task a human is also editing.

Key parameters

  • Task ID: the task to modify, inside the list named in TaskList Name or ID.
  • Update Fields: Status flips a task to completed, Due Date pushes a deadline, Title and Notes rewrite the content, Previous moves the task after another sibling.
Use cases
a page marked done in Notion updates the matching task status, so the two lists agree without anyone copying between them.
Need help

Need help automating Google Tasks with n8n?

A person reads every message.

FAQ

Google Tasks and n8n, the usual questions

01Is the Google Tasks n8n integration free?
Yes on the n8n side. The Google Tasks node ships with n8n, so there is nothing to install and nothing extra to pay for the connector itself, on n8n Cloud as well as on a self-hosted instance running the Community Edition under the Sustainable Use license. What you pay for is the platform: a Cloud plan, or the server you run n8n on when you host it yourself. The 5 operations behave the same in both cases, and a workflow built on Cloud runs unchanged on your own instance.
02What credentials does the Google Tasks node need?
A Google credential, created once in n8n and reused by every node that talks to that account. Two routes exist. On n8n Cloud, Managed OAuth2 means clicking Sign in with Google on the credential screen, with no configuration in the Google Cloud Console. Self-hosted, you build a custom OAuth2 credential: a Google Cloud project, the APIs enabled, the OAuth consent screen filled in, an OAuth client ID of type Web application, and the OAuth Redirect URL from n8n pasted into the authorized redirect URIs. Google service nodes also document a Service Account method, built from the client_email and private_key of a downloaded JSON key, though n8n supports it on fewer nodes than OAuth2.
03What are the limits of the Google Tasks node in n8n?
Three, and they are easy to plan around. The node covers one resource, Task, so anything about the task lists themselves is out of scope: creating a list or enumerating the lists of an account has no operation here, and those calls go through the HTTP Request node, which reaches any endpoint of the API while reusing the same credential. On Get many tasks, leaving Return All off caps the result at Limit. And every operation needs the list plus, for get, update and delete, the Task ID that Google returns, never the title you read on screen.
04Does Google Tasks have a trigger node in n8n?
No. Google Tasks has no trigger node, so no workflow starts because a task changed in Google. Three ways around it. A Schedule Trigger runs Get many tasks at a fixed interval and compares what comes back, using Updated Min to look only at what moved since the last run. An n8n Webhook, meaning a URL another service calls, starts the workflow from the tool where the work originates. Or another tool's own trigger does the job, which is the common case: a new email, a new row, a new record, and Google Tasks is the destination rather than the starting point.
05n8n or Make for Google Tasks?
It depends on where you want the data and how you want to pay. Make is hosted only, with no self-hosting option, and is billed per operation, so a workflow that reads a full task list every hour has a cost that follows its volume. n8n runs on Cloud or on your own server, which matters when task titles and notes carry client information you would rather keep in house, and the pricing model is not a per-operation meter. Both build visually. The practical test is a boring one: take your busiest list, count the operations a day of automation would consume, and compare that with what an instance costs you.
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