Sync Google Tasks with Notion: every method compared [2026]

Google Tasks captures fast. Notion organizes deep. Bridging the two requires a third-party tool because Notion does not ship a native Google Tasks integration. This article compares all nine working methods on what actually matters for a task sync: two-way support, subtask hierarchy, recurring-task semantics, multi-list support, and field depth. Each method gets a row in the comparison table, an honest pro/con breakdown in its own section, and a place in the use-case decision tree further down.

The 9 ways to sync Google Tasks with Notion

Nine working methods as of May 2026. The table scores them on what readers actually care about: whether they sync both ways, whether they preserve subtask hierarchy, whether they handle Google Tasks's moving-date recurring semantics, how many fields they expose, and whether they support multiple Google Tasks lists.

Only 2sync clears all five. Pleexy markets two-way and admits otherwise in its own FAQ (covered below). Zapier, Make, IFTTT, and TaskClone are one-way per recipe. n8n and the GitHub scripts can be made to work two-way but require hours of code and accept admitted gaps. Manual copy-paste is not a sync.

How each method actually works

1. Manual copy-paste, embed bookmark, web clipper

Three flavors, none qualifies as a sync.

Copy-paste moves tasks one time. Embedding https://tasks.google.com as a Notion bookmark gives you a clickable link, not database items. The Notion Web Clipper saves a Google Tasks page as a Notion page snapshot. Every change after the first transfer has to be made twice. Use these only when you genuinely need a one-time move and will never touch the data again.

2. Pleexy

Pleexy is one of the better-known third-party sync tools between Google Tasks and Notion. The way it actually works: tasks you create in Notion sync to Google Tasks, and subsequent edits and completions echo both ways. Tasks you create directly in Google Tasks, however, do not appear in Notion: Pleexy's own documentation flags task creation from Google Tasks to Notion as a missing feature still in their backlog.

This makes Pleexy partially two-way (for updates) but one-way for task creation. The constraint matters if your common workflow is capturing tasks on your phone in Google Tasks and seeing them in Notion: that direction does not work with Pleexy.

Other Pleexy limits, per their docs: no subtask hierarchy preservation, no field-level direction control surfaced in the wizard, no time-of-day on due dates (Pleexy attributes this to the Google Tasks API; other tools work around it). Multi-list mapping is supported.

Pricing: $4/month monthly or $3.33/month annual.

Pick Pleexy if you plan tasks in Notion, push them to Google Tasks for mobile capture, and never add tasks from the Google Tasks side.

3. Zapier

Zapier offers Zap templates in both directions, each one one-way: "when a new task is added in Google Tasks, create a page in Notion." The reverse needs a second Zap, and updates to existing tasks need more Zaps still. Two Zaps stitched together is not the same as a real two-way sync; the recipes can fight each other on the same task, deletions need their own logic, and recurring tasks create a new Notion page per occurrence.

Free tier: 100 tasks/month with 15-minute polling. Paid tiers raise the cap and shorten polling (as fast as 1-minute on Pro).

No subtask hierarchy, no field-level direction control, no recurring-task semantics that match Google Tasks's moving-date model.

For a wider shortlist of alternatives, see Zapier alternatives for Notion.

4. Make

Make (formerly Integromat) replaces Zapier's recipe builder with a visual scenario canvas. Scenarios can chain multi-step logic, transform data between modules, and route conditionally. The trade-off is a steeper learning curve.

Make hits the same structural ceiling as Zapier on this integration: one-way per scenario, no native two-way construct, no subtask hierarchy, no recurring-task semantics. The visual canvas just makes the one-way flows more sophisticated.

Free tier: 1,000 credits/month (Make rebranded "operations" to "credits"), max 2 active scenarios, 15-minute minimum interval between runs. Paid plans start at $9/month.

Use Make if your task-routing logic is genuinely complex (filter by tag, split by list, transform titles, fan out to multiple databases) and you accept building each direction as its own scenario. For the head-to-head with Zapier, see Zapier vs Make.

5. IFTTT

IFTTT is the simplest tier of the automation platforms. Applets trigger on a single Google Tasks event and write to Notion, or the reverse. The pre-built applets cover title and completion status, nothing beyond.

Works if your entire need is one trigger ("new Google Tasks task → new Notion page") and you do not care about subtasks, descriptions, or due dates.

Free tier: 2 applets total (yes, two). Pro is $2.99/month for 20 applets; Pro+ is $8.99/month for unlimited.

For anything richer than a single trigger, Zapier and Make do more for similar effort.

6. TaskClone

TaskClone serves a different niche from everything else in this list. It does not sync Notion databases with Google Tasks. It extracts [ ] checkbox items from Notion page content (meeting notes, project briefs, daily journals) and pushes them to Google Tasks as new tasks. Completion status echoes back on the Professional tier.

If you keep tasks as checkbox items inside Notion notes rather than as rows in a Notion database, TaskClone is the right shape. For anyone with a Notion task database, it is the wrong category; your existing database properties are invisible to it, and the resulting Google Tasks are unconnected to any structured data on the Notion side.

Pricing: 14-day free trial, then Starter $1.99/month (annual billing only); Professional $2.99/month for two-way completion sync. No free tier.

7. n8n

n8n is a self-hosted (or cloud-hosted on n8n.cloud) automation platform with a community workflow library. The Google Tasks + Notion node directory exposes triggers and actions; building a real two-way sync requires writing the reverse flow yourself plus deduplication logic.

n8n suits developers who already self-host, want the source code, and can invest several hours in field mapping and edge cases.

The self-hosted Community Edition is free with unlimited executions; n8n.cloud has no permanent free tier (14-day trial only, then €20/month Starter billed annually for 2,500 executions; month-to-month runs higher).

For the cloud-vs-self-host decision in general, see Zapier vs n8n.

8. Free DIY GitHub scripts

Three free open-source projects cover this integration at the API level:

• nathan-dykstra/gtasks-notion-integration: a Python script with manual one-time setup. Active repo. The README is explicit about two limits: "Google API limitations means I can't sync the time part of a Notion task date to Google Tasks" and "the 'Status' property syncs only To-do and Completed statuses because Google Tasks does not have intermediate stages."
• aantipov/notion-google-tasks-worker: a Cloudflare Worker runtime. Archived by the owner in April 2025; no longer maintained. Fork at your own risk.
• notion-google-tasks-sync.com: a free hosted version. Syncs title, date, and status only. Single Notion database to single Google Tasks list. Site availability has been intermittent.

Use a DIY script if you are a developer, the API-level approach appeals to you, and you accept the documented gaps. Most readers want a no-code tool with the time, status, subtask, and recurrence layers handled by someone else.

9. 2sync

2sync is purpose-built for Notion database sync. The full walkthrough is in the next section; the short version of why it wins the scoring:

• Full two-way for every direction, not Pleexy's one-way-with-completion-echo masquerading as two-way.
• 15 mapped fields with per-field direction control. Seven core Google Tasks fields, seven optional metadata fields, one Notion-side deletion trigger.
• Subtask hierarchy preserved through a Notion Relation property pointing at the same database. No other tool in this list does this.
• Recurring tasks handled with Google Tasks's own moving-date semantics. Same Notion page persists across occurrences, date advances on completion, checkbox resets. Zapier, Make, and IFTTT duplicate the page on every occurrence.
• Multi-list support with a default-list setting for tasks created on the Notion side.
• Shared connections for teams. One setup, each member connects their own Google Tasks lists.

Notion lists 2sync in its official integrations directory, which is as close to a Notion endorsement as a third-party sync tool gets. Of all active 2sync users, 78.9% choose two-way sync, not one-way.

How to set up 2sync

Before starting, you need a Notion account (with permission to authorize integrations in the target workspace), a Notion database for tasks (existing or new; 2sync provides a template), a Google account with the task lists you want to sync, and a 2sync account.

Step 1: Start a new automation

1. Go to 2sync and click Start automating now.
2. Choose the Google Tasks automation from the catalog.

Step 2: Connect Google Tasks

1. Click Connect Google Tasks. The Google OAuth window opens.
2. Sign in with the Google account that owns the task lists you want to sync.
3. Grant the requested permissions. 2sync needs read and write access to your Google Tasks. These permissions do not give 2sync access to Gmail, Drive, or other Google data.
4. Pick which task lists to include. Toggle each list on or off, and choose a default for new tasks created from Notion.
5. Click Continue.

Step 3: Connect Notion

1. Pick your Notion workspace from the Connected as dropdown.
2. Choose the Notion database that will hold your synced Google Tasks tasks.
3. Click Continue.

Step 4: Map fields

Pick the overall flow at the top of the field-mapping screen: One-way to Notion, Two-way sync, or One-way to Google Tasks. Blue arrows show active directions for each field; grey arrows are disabled in the current mode. Set the mode first, then fine-tune individual rows.

The wizard ships with smart defaults that pre-map the most-used fields (Task Title, Completed, Completed At, Automation Name) so you can start syncing immediately. Add Due Date, Parent Task, Task List, and any of the optional metadata fields as you need them. The full 15-field reference (which Notion property types each accepts, and which direction they sync) is in the next section. Click Continue when done.

Step 5: Filters (optional)

Filters control exactly which Notion pages sync to Google Tasks. Start broad, run for a short period, then tighten if there is noise.

Pick the logic mode at the top (Any, All, or None of the following are true), then add conditions. The filter dimensions are Notion-side: Task Title, Task Project Name, Task Description, or any Notion property value (Status, Priority, custom Selects, checkboxes). Common patterns: only sync Notion pages whose Task Title contains "Meeting" or "Project," only sync tasks where a Status property equals "To Do," or scope by a Project relation when the Notion database doubles as a project tracker.

Step 6: Defaults (optional)

When 2sync creates a new Notion page from a Google Tasks task, you can pre-fill static values for Notion-side properties. Defaults apply only to newly created pages, never to existing ones.

Two defaults pay off on most setups. Page Icon sets the emoji every new Notion page opens with; a checkmark glyph (✅) makes synced Google Tasks visually distinct from manually-created pages. Source (Select) tags every synced page with "Google Tasks" so you can filter, group, or roll up by where the page came from, especially useful when you sync Google Tasks alongside Todoist or Google Calendar into the same database.

Step 7: Sync settings

The last step is Sync settings. Click Show advanced settings to reveal the full set.

The settings worth setting on the first sync:

• Automation name. Rename from the default "Google Tasks & Notion Sync" to something specific if you plan to run more than one (for example "GT Work → Notion Tasks").
• Add Notion link below every description. Inserts the Notion page URL into the Google Tasks task notes so you can jump from a task back to the Notion page. Around half of our users enable this.
• Sync Notion entries that were created before the first sync. Off by default; turn it on to backfill the automation with Notion entries that pre-date the setup.
• Sync completed tasks up to. Defaults to 7 days behind. We only sync completed tasks within this date range; older completions are ignored so the database does not fill up with closed work you no longer need to see. Larger windows are available but slow down the sync.
• Allow task deletion. Disabled by default for safety; off means deleting in either tool only un-syncs the items. Turn it on once you trust the setup.
• Sync frequency. 5 minutes on Solo, 3 minutes on Premium, 2 minutes on Pro.
• Ignore Notion entries linked with other automations. On by default; prevents duplicates when you run more than one automation into the same Notion database.

Run the test sync to confirm everything looks right, then click Continue to start the sync. You are live.

The 15 fields 2sync can sync

The wizard exposes 15 fields total: seven core Google Tasks fields (sync both ways out of the box), seven optional metadata fields (off by default; turn them on to enrich Notion-side context), and one Notion-side deletion trigger that runs the other direction.

Core data fields:

Wizard metadata fields (optional):

Control field:

The full per-field behavior, including the rich-text-to-plain-text conversion on Description, the recurring-task survival semantics, and the parent-task relation depth, is documented in the Google Tasks field reference.

Which method should you choose?

The right method depends on what you actually need. Pick the row that matches your situation.

• You only ever push tasks from Notion to Google Tasks and never the other way: Pleexy works (and the contradiction in its FAQ does not apply to your direction). Cheap, simple. Caveat: still no subtask hierarchy, no time-of-day, no field-level control.
• You need bidirectional sync (most common case): 2sync. It is the only method in this list that delivers what Pleexy markets. The 7-step walkthrough above gets you running in about 10 minutes.
• You already pay for Zapier or Make and the volume is small: build a one-way Zap or scenario. Accept that you will hit the limits (no subtasks, no recurring semantics, no field depth) and budget for the upgrade to 2sync when you do.
• You capture tasks as [ ] checkboxes inside Notion page notes rather than as rows in a Notion database: TaskClone is purpose-built for that shape. Wrong category for anyone with a Notion task database.
• You self-host n8n already, or you want to write the integration yourself: n8n + the GitHub scripts cover that path. You will trade hours of code for the freedom to customize every field and edge case.
• You want free and you are willing to live with admitted gaps: the GitHub scripts work. No time-of-day on due dates, no intermediate status values, no subtask hierarchy. If that is acceptable, the scripts are free and the code is yours.
• You need team workflows where everyone connects their own Google Tasks lists to one Notion database: only 2sync supports shared connections. Pleexy is single-user; the automation platforms scale poorly across team members.

Advanced workflows

Four scenarios that 2sync handles natively and the alternatives above either do not handle or break on.

Multiple Google Tasks lists into one Notion database

Sync work, personal, and project-specific lists into a single Notion database. The Task List field marks which list each task came from; filter your Notion views by list to keep contexts visually separate. The default-list setting controls which Google Tasks list receives new tasks created on the Notion side. The average 2sync user syncs 4.13 calendars or lists per workspace, typically a mix.

Subtask hierarchy preserved in Notion

Google Tasks supports one level of subtask nesting (enforced by the API; this is a Google constraint, not a 2sync one). 2sync maps the Parent Task field to a Notion Relation property pointing at the same database, so subtask pages link to their parent. Rollups on the parent page can show subtask counts, completion percentages, or any aggregated property from the children (the mechanics are walked through in how to create sub-tasks in Notion). Completing a parent task in Google Tasks completes its subtasks (Google's behavior); 2sync reflects that in Notion automatically. 39.3% of active 2sync users use relation property mapping to build dashboards on top of their synced tasks.

Recurring tasks survive the sync without duplicating

Google Tasks stores recurring tasks as a single task with a moving due date that advances on completion. 2sync mirrors that exact behavior in Notion: the same Notion page persists, the date advances to the next occurrence, the Completed checkbox resets automatically. You always see the current occurrence, not a backlog.

This matters because Zapier, Make, and IFTTT create a new Notion page on every occurrence. Over a year, a weekly recurring task becomes 52 Notion pages cluttering the database. With 2sync it stays one. For how recurring tasks behave at the source, see Recurring tasks in the complete guide; if you want to build the recurrence pattern natively in Notion alongside Google Tasks, how to create recurring tasks in Notion walks through the database-template and automation routes.

Team workflows with shared connections

One person sets up the Notion database and the 2sync automation, then shares a connection link. Each team member connects their own Google Tasks lists to the same Notion database, no duplicated configuration, no admin access required. Create per-person filtered views in Notion so each teammate sees only their own tasks, plus a team-wide view that rolls up everyone. This is how Google Tasks gains the shared-list feature it does not have natively.

If your stack mixes providers (some teammates on Todoist, some on Google Tasks, calendar events alongside), run additional automations to the same Notion database: how to sync Notion with Todoist and how to sync Notion with Google Calendar cover those flows. The automations run independently and a Source field in Notion distinguishes which app each page came from.

Troubleshooting the issues specific to Google Tasks sync

Most "sync not working" causes are generic (revoked OAuth permissions, filter conditions excluding the tasks you expected, a sync still on its first cycle). Reconnect from the 2sync dashboard, check filters, wait 2 to 5 minutes for the first cycle. The issues below are specific to Google Tasks.

Recurring tasks creating duplicate Notion pages

This is the Zapier / Make / IFTTT failure mode, not a 2sync one. If you see duplicate Notion pages for a recurring task with 2sync as the sync layer, verify that no parallel Zapier or Make automation is also writing to the same Notion database. The fix is to remove the parallel automation; 2sync's single Notion page with a moving date is the correct behavior.

Subtasks syncing as flat tasks instead of linking to their parent

Confirm the Parent Task field is mapped to a Notion Relation property (not Text or Select) pointing at the same Notion database. If the Parent Task field is unmapped, subtasks sync as flat tasks with no relation to their parent.

Task times not syncing

Confirm your Notion Date property is configured to accept time-of-day values, not date-only. Then check the time-zone settings in both Google and Notion; mismatches can shift tasks by hours. (Free DIY GitHub scripts do not sync times at all per their READMEs; 2sync does.)

Deletion not propagating

By default, deletion in either app only un-syncs the pair so you keep a record of completed work. If you want deletions to propagate, turn on Allow task deletion in the automation's advanced settings. For controlled deletion from the Notion side, map the Trigger deletion on Google Tasks field to a dedicated Notion checkbox and set it intentionally.

Description formatting lost

Google Tasks notes are plain text only. Rich-text formatting in Notion (bold, headings, lists) is preserved on the Notion side but flattened to plain text when written to Google Tasks. This is a Google Tasks API constraint, not a 2sync one. Keep formatted notes on the Notion side and use plain-text notes on the Google Tasks side.

Conclusion

Scored on two-way support, subtask hierarchy preserved through Notion relations, recurring tasks handled the way Google Tasks itself handles them, multi-list support, shared connections for teams, and 15 mapped fields with per-field direction control, only one method clears the full bar: 2sync.

If you need bidirectional sync (the most common case), 2sync's Google Tasks integration is the most complete option available today.

For related reading:

• Still picking your task tool? Todoist vs Google Tasks walks through the head-to-head, and the best to-do list apps covers the broader field.
• Sync more than Google Tasks? How to sync Notion with Google Calendar, how to sync Notion with Todoist, and how to sync Notion with Outlook Calendar cover parallel territory and run side by side without conflict.
• Google Tasks basics (lists, recurring, subtasks, the iPhone widget, sharing workarounds) live in Google Tasks: the complete guide.

FAQ