Google Tasks fields that sync to Notion
All 7 Google Tasks fields that sync to Notion with 2sync: property types, sync directions, and how to use task lists, subtasks, and completion tracking
2sync syncs 7 Google Tasks fields to Notion, including task title, notes, due date, completion status, task list, and parent task relationships. Most fields support two-way sync, so you can manage tasks in either Google Tasks or Notion. Task List and Completed At are read-only, syncing from Google Tasks to Notion only. You control each field's direction in field mapping.
Synced fields
| Field | Notion property type | Sync direction |
|---|---|---|
| Task Title | Title | Two-way |
| Notes | Rich Text | Two-way |
| Due Date | Date | Two-way |
| Completed | Checkbox | Two-way |
| Completed At | Date | To Notion |
| Task List | Select | To Notion |
| Parent Task | Relation | Two-way |
You can set each field to two-way, one-way to Notion, or one-way to Google Tasks. Adjust this per field in your automation's field mapping settings.
Task title
The Task Title field maps to Notion's Title property, the main name of each database page. Changes to the task name in either app update the other automatically.
Notes
The Notes field maps to Rich Text. Google Tasks notes are plain text with no formatting. Any rich text formatting added in Notion (bold, italic, lists) is converted to plain text when syncing back to Google Tasks.
Changing a field's sync direction after initial setup does not retroactively update existing items. Only new changes follow the updated direction.
Due date
The Due Date field maps to Notion's Date property and syncs in both directions.
Google Tasks supports due dates with or without times. Date-only entries appear as all-day items in Notion, while dates with specific times include the time component. Setting a due date in either app updates the other on the next sync cycle.
For recurring tasks, completing the task advances the due date to the next occurrence automatically. The same Notion page updates with the new date rather than creating a new row. You always see the current occurrence, not future ones.
Completed
The Completed field syncs as a Checkbox in both directions. Checking it in Notion marks the task as done in Google Tasks. Completing a task in Google Tasks checks the box in Notion.
The Completed At field records when the task was finished. This field is read-only and set automatically by Google Tasks. It syncs to Notion as a Date property.
For recurring tasks, completing the task resets the Completed checkbox and advances the due date to the next occurrence. Completed At reflects the most recent completion.
Task list
The Task List field identifies which Google Tasks list a task belongs to and syncs as a Select property in Notion. When you sync multiple task lists into one Notion database, this field lets you filter and group tasks by list.
Task List is read-only in Notion. To move a task between lists, make the change in Google Tasks directly.
Parent task (subtasks)
Google Tasks supports a single level of nesting: tasks can have subtasks. Map the Parent Task field to a Relation property to preserve this hierarchy in Notion.
Subtasks sync as individual pages with a relation pointing to their parent. Creating a relation between two tasks in Notion establishes the parent-child link in Google Tasks. Use Notion rollups on the relation to display subtask counts or completion percentages.
Google Tasks supports one level of nesting only. You can have tasks with subtasks, but subtasks cannot have their own subtasks. This limitation comes from the Google Tasks API.
What should I do next?
Now that you know which fields sync:
- Set up your Google Tasks sync if you haven't connected yet
- Configure sync direction per field
- Set default values for empty fields
Related
- Google Tasks sync for the full setup guide
- Todoist fields for comparing Todoist's field set
- Notion property types for supported property formats
- Default values for setting fallback values on empty fields
- Relations for connecting subtasks via relational databases
- Sync direction for per-field data flow control
FAQ
Can I sync multiple task lists to one Notion database?
Yes. Select multiple task lists in your automation settings. Each list syncs to the same database, and the Task List field identifies which list each task belongs to.
Does Google Tasks support recurring tasks?
Google Tasks has limited recurrence support. It stores one task with a moving due date. When you complete a recurring task, the same Notion page updates with the next due date rather than creating a new task.
Why can't I move tasks between lists from Notion?
The Task List field is read-only because Google Tasks treats list assignment as a structural property. Move tasks between lists in Google Tasks directly, and the change syncs to Notion.
How deep can subtask nesting go?
Google Tasks supports one level of nesting only. You can have tasks with subtasks, but subtasks cannot have their own subtasks. This limitation comes from the Google Tasks API.
Can I add new fields to the sync?
No. You can only sync the 7 fields listed above. Custom Google Tasks fields are not supported. However, you can add Notion-only properties to your database for additional tracking.
What happens when I complete a task in Notion?
Checking the Completed checkbox in Notion marks the task as done in Google Tasks on the next sync. The Completed At date is set automatically. For recurring tasks, the due date advances to the next occurrence and the checkbox resets.
Why is Notes plain text only?
Google Tasks does not support rich text formatting in its notes field. Any bold, italic, or list formatting added in Notion is converted to plain text when syncing back to Google Tasks.
Does the Due Date field support times?
Yes. Google Tasks supports due dates with or without times. Date-only entries appear as all-day items in Notion, while dates with specific times include the time component.