Google Tasks provides a simple to-do list and task management system integrated into Gmail and Google Calendar for quick and easy tracking
Google Tasks provides a simple to-do list and task management system integrated into Gmail and Google Calendar for quick and easy tracking On Nagent, Google Tasks is exposed as a fully-configurable task management integration that any agent can call — 18 actions, 5 triggers, and OAuth authentication. No code is required to wire Google Tasks into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Google Tasks to automate the kinds of tasks task management teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Google Tasks also supports 4 event triggers ("New Task Created", "New Task List Created", "Task Details Changed", and more), which lets your Nagent agents react to Google Tasks activity in real time — for example, kicking off a downstream workflow the moment a relevant event fires.
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Google Tasks into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Triggers are the entry points of agents built on Nagent — pick one to fire your agent the moment a Google Tasks event happens. Webhook triggers run instantly; poll triggers check on an interval you configure. Each shows its configuration parameters and the payload your agent receives.
GOOGLETASKS_NEW_TASK_CREATED_TRIGGERTriggers when a new task is created in a Google Tasks list. Uses timestamp filtering (updatedMin) to efficiently detect new tasks.
Configuration
Periodic Interval to Check for Updates & Send a Trigger in Minutes
Maximum number of tasks to check in each poll (1-100)
Identifier of the task list to monitor. Use '@default' for the primary task list or provide a specific task list ID from list_task_lists action.
Payload
Type of event that occurred
The newly created task
GOOGLETASKS_NEW_TASK_LIST_CREATED_TRIGGERTriggers when a new Google Tasks task list is created. This trigger monitors Google Tasks and fires when new task lists are detected.
Configuration
Periodic Interval to Check for Updates & Send a Trigger in Minutes
Maximum number of task lists to check in each poll (1-100)
Payload
Type of event that occurred
The newly created task list
GOOGLETASKS_TASK_DETAILS_CHANGED_TRIGGERTriggers when a specific task's details change. This trigger monitors a single Google Task and fires when any of its details (title, notes, status, due date, completion, position) are modified.
Configuration
Periodic Interval to Check for Updates & Send a Trigger in Minutes
The ID of the specific task to monitor for changes
The ID of the task list containing the task to monitor
Payload
List of field names that changed
Type of event that occurred
The previous task snapshot (None on first poll)
The current task with all details
GOOGLETASKS_TASK_LIST_CHANGED_TRIGGERTriggers when a task list changes (title or content updates). This trigger monitors a specific Google Tasks list and fires when changes are detected.
Configuration
Periodic Interval to Check for Updates & Send a Trigger in Minutes
The unique identifier of the task list to monitor for changes. Use '@default' for the default task list.
Payload
List of fields that changed (e.g., 'title', 'updated')
Type of event that occurred
The task list with changed state
GOOGLETASKS_TASK_UPDATED_TRIGGERTriggers when an existing task is updated in a Google Tasks list. This trigger monitors a specific task list and fires when tasks are modified.
Configuration
Periodic Interval to Check for Updates & Send a Trigger in Minutes
Maximum number of tasks to check in each poll (1-100)
Include completed tasks in the monitoring. Defaults to true.
Include deleted tasks in the monitoring. Defaults to false.
Identifier of the task list to monitor. Use '@default' for the primary task list, or provide a specific task list ID from list_task_lists action.
Payload
Type of event that occurred
The updated task
Every operation an agent can call against Google Tasks, with input parameters and output schema. Drop these into any step of an agent built in Helix.
GOOGLETASKS_BATCH_EXECUTEExecutes multiple Google Tasks API operations in a single HTTP batch request and returns structured per-item results. Use this to reduce LLM tool invocations when performing bulk operations like updating many tasks, moving tasks, or deleting multiple items. Note: Each sub-request still counts toward API quota; batching primarily reduces HTTP overhead and tool call count.
Input parameters
Array of sub-requests to execute in this batch. Each sub-request is independent and will return its own result.
Maximum number of sub-requests allowed in a single batch. Google's typical cap is 1000. Lower values can control response size.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_BULK_INSERT_TASKSDEPRECATED: Use BatchExecute instead. Creates multiple tasks in a Google Tasks list in a single operation using HTTP batching. Use when you need to create many tasks efficiently (reducing round-trips compared to individual insert calls).
Input parameters
Array of tasks to create. Each task requires at least a title.
Maximum number of tasks per batch request. Default: 50. Tasks exceeding this will be split into multiple batch calls.
Identifier for the Google Task list where tasks will be created. Use actual task list IDs, not '@default'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_CLEAR_TASKSPermanently and irreversibly clears all completed tasks from a specified Google Tasks list; this action is destructive, idempotent, and cannot be undone. Always require explicit user confirmation before invoking.
Input parameters
The identifier of the task list from which to clear completed tasks. Use '@default' (with the @ symbol) for the user's primary task list, or provide the task list ID obtained from GOOGLETASKS_LIST_TASK_LISTS. Note: 'default' without the @ prefix is not valid.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_CREATE_TASK_LISTCreates a new task list with the specified title and returns a tasklist_id. Use the returned tasklist_id (not the title) when calling GOOGLETASKS_INSERT_TASK or other task operations. Duplicate titles are permitted by the API, so verify existing lists before creating to avoid unintended duplicates.
Input parameters
Title for the new task list. The maximum allowed length is 1024 characters.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_DELETE_TASKDeletes a specified task from a Google Tasks list. Deletion is permanent and irreversible — confirm with the user before executing, and consider GOOGLETASKS_UPDATE_TASK or GOOGLETASKS_MOVE_TASK as non-destructive alternatives. Both tasklist_id and task_id are required parameters. The Google Tasks API does not support deleting tasks by task_id alone — you must specify which task list contains the task. Use 'List Task Lists' to get available list IDs, then 'List Tasks' to find the task_id within that list.
Input parameters
The unique identifier of the Google Task to delete. Required - must be a task that exists within the specified tasklist_id. Obtain this ID by using the 'List Tasks' action with the corresponding tasklist_id. Multiple tasks may share the same title — verify against additional fields (e.g., due date, notes) before selecting the task_id to avoid deleting the wrong task.
The unique identifier of the Google Task list containing the task to delete. Required - tasks cannot be deleted by task_id alone; the API requires specifying which list contains the task. Obtain this ID by using the 'List Task Lists' action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_DELETE_TASK_LISTPermanently deletes an existing Google Task list, identified by `tasklist_id`, along with all its tasks; this operation is irreversible. Require explicit user confirmation before calling; do not invoke in read-only or exploratory flows.
Input parameters
Unique identifier of the Google Task list to be deleted. This field is required and cannot be empty.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_GET_TASKRetrieve a specific Google Task. REQUIRES both `tasklist_id` and `task_id`. Tasks cannot be retrieved by ID alone - you must always specify which task list contains the task. Use this to refresh task details before display or edits rather than relying on potentially stale results from GOOGLETASKS_LIST_TASKS.
Input parameters
REQUIRED. Unique identifier of the Google Task to retrieve. Must be used together with tasklist_id.
REQUIRED. Unique identifier of the Google Tasks list containing the task. You must always provide this parameter - tasks cannot be retrieved by task_id alone.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_GET_TASK_LISTRetrieves a specific task list from the user's Google Tasks if the `tasklist_id` exists for the authenticated user.
Input parameters
The unique identifier of the task list to retrieve, assigned by Google Tasks when the list is created.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_INSERT_TASKCreates a new task in a given `tasklist_id`, optionally as a subtask of an existing `task_parent` or positioned after an existing `task_previous` sibling, where both `task_parent` and `task_previous` must belong to the same `tasklist_id` if specified. IMPORTANT: Date fields (due, completed) accept various formats like '28 Sep 2025', '11:59 PM, 22 Sep 2025', or ISO format '2025-09-21T15:30:00Z' and will automatically convert them to RFC3339 format required by the API. Not idempotent — repeated calls with identical parameters create duplicate tasks; track returned task IDs to avoid duplication. High-volume inserts may trigger 403 rateLimitExceeded or 429; apply exponential backoff.
Input parameters
Unique identifier for the task. Generated by Google Tasks API when creating a task. Used for updating or deleting existing tasks.
Due date for the task (optional). NOTE: Google Tasks only stores the date portion (YYYY-MM-DD) - any time component provided will be automatically stripped before sending to the API. Google Tasks API requires dates in RFC3339 format (e.g., 2025-09-22T13:48:27Z). We automatically convert various human-readable formats to RFC3339: Accepted formats: • 2025-09-28T23:59:00Z → RFC3339/ISO-8601 format (preferred) - September 28, 2025 at 11:59 PM UTC • 28 Sep 2025 → Simple date format - Will be converted to midnight UTC on that date • 11:59 PM, 22 Sep 2025 → Time with date - Assumes UTC timezone if not specified • 1:00 PM, 21 Sep 2025 → 12-hour format with date - Converted to 13:00 UTC • UTC-5:30, 6:50 PM → With timezone offset - Converted to UTC automatically • UTC+1, 11:59 PM, 31 Dec → Timezone with date - Next occurrence of Dec 31 • 2025-09-21T15:30:00+02:00 → RFC3339 with timezone offset Note: If no timezone is specified, UTC is assumed. Dates without times default to midnight UTC.
ETag of the resource for concurrency control. Prevents accidental overwrites when multiple clients modify the same task. Auto-generated by the API.
Additional details or description for the task. Supports plain text only (no HTML/markdown). Maximum 8192 characters. Example: 'Include Q3 sales data and projections'
Title/name of the task (REQUIRED). This is the main text displayed for the task. Maximum 1024 characters. Example: 'Complete quarterly report'
Whether the task is hidden from the default view. Hidden tasks can still be accessed via API but won't show in UI. Default: false
Status of the task. Must be either 'needsAction' (task is pending) or 'completed' (task is done). Defaults to 'needsAction' if not provided.
Whether the task has been deleted. Deleted tasks are marked but not immediately removed, allowing for recovery. Default: false
Date/time when the task was marked as completed. Only applicable when status='completed'. Unlike 'due', this field preserves the time component. Google Tasks API requires dates in RFC3339 format (e.g., 2025-09-22T13:48:27Z). We automatically convert various human-readable formats to RFC3339: Accepted formats: • 2025-09-28T23:59:00Z → RFC3339/ISO-8601 format (preferred) - September 28, 2025 at 11:59 PM UTC • 28 Sep 2025 → Simple date format - Will be converted to midnight UTC on that date • 11:59 PM, 22 Sep 2025 → Time with date - Assumes UTC timezone if not specified • 1:00 PM, 21 Sep 2025 → 12-hour format with date - Converted to 13:00 UTC • UTC-5:30, 6:50 PM → With timezone offset - Converted to UTC automatically • UTC+1, 11:59 PM, 31 Dec → Timezone with date - Next occurrence of Dec 31 • 2025-09-21T15:30:00+02:00 → RFC3339 with timezone offset Note: If no timezone is specified, UTC is assumed. Dates without times default to midnight UTC.
Identifier of an existing task to serve as parent; if provided, creates a subtask, otherwise a top-level task in the specified list.
Task list identifier where the new task will be created. Valid values: (1) '@default' - special identifier that references the user's default/primary task list, or (2) an actual task list ID obtained from the 'List Task Lists' action (GOOGLETASKS_LIST_TASK_LISTS). Task list IDs are opaque strings generated by Google (typically base64-encoded, e.g., 'MDQ1NTEzMjc4OTM5MzM0NTY4NzE6MDow').
Identifier of an existing task after which the new task will be placed, at the same hierarchical level (as a sibling).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_LIST_ALL_TASKSTool to list all tasks across all of the user's task lists with optional filters. Use when the agent needs to see all tasks without knowing which list to query first. Each returned task is annotated with its tasklist_id and tasklist_title for context.
Input parameters
Only include tasks due on or before this date. Google Tasks API requires dates in RFC3339 format (e.g., 2025-09-22T13:48:27Z). We automatically convert various human-readable formats to RFC3339: Accepted formats: • 2025-09-28T23:59:00Z → RFC3339/ISO-8601 format (preferred) - September 28, 2025 at 11:59 PM UTC • 28 Sep 2025 → Simple date format - Will be converted to midnight UTC on that date • 11:59 PM, 22 Sep 2025 → Time with date - Assumes UTC timezone if not specified • 1:00 PM, 21 Sep 2025 → 12-hour format with date - Converted to 13:00 UTC • UTC-5:30, 6:50 PM → With timezone offset - Converted to UTC automatically • UTC+1, 11:59 PM, 31 Dec → Timezone with date - Next occurrence of Dec 31 • 2025-09-21T15:30:00+02:00 → RFC3339 with timezone offset Note: If no timezone is specified, UTC is assumed. Dates without times default to midnight UTC.
Only include tasks due on or after this date. Google Tasks API requires dates in RFC3339 format (e.g., 2025-09-22T13:48:27Z). We automatically convert various human-readable formats to RFC3339: Accepted formats: • 2025-09-28T23:59:00Z → RFC3339/ISO-8601 format (preferred) - September 28, 2025 at 11:59 PM UTC • 28 Sep 2025 → Simple date format - Will be converted to midnight UTC on that date • 11:59 PM, 22 Sep 2025 → Time with date - Assumes UTC timezone if not specified • 1:00 PM, 21 Sep 2025 → 12-hour format with date - Converted to 13:00 UTC • UTC-5:30, 6:50 PM → With timezone offset - Converted to UTC automatically • UTC+1, 11:59 PM, 31 Dec → Timezone with date - Next occurrence of Dec 31 • 2025-09-21T15:30:00+02:00 → RFC3339 with timezone offset Note: If no timezone is specified, UTC is assumed. Dates without times default to midnight UTC.
Include hidden tasks in results. Defaults to false.
Only include tasks updated on or after this date. Google Tasks API requires dates in RFC3339 format (e.g., 2025-09-22T13:48:27Z). We automatically convert various human-readable formats to RFC3339: Accepted formats: • 2025-09-28T23:59:00Z → RFC3339/ISO-8601 format (preferred) - September 28, 2025 at 11:59 PM UTC • 28 Sep 2025 → Simple date format - Will be converted to midnight UTC on that date • 11:59 PM, 22 Sep 2025 → Time with date - Assumes UTC timezone if not specified • 1:00 PM, 21 Sep 2025 → 12-hour format with date - Converted to 13:00 UTC • UTC-5:30, 6:50 PM → With timezone offset - Converted to UTC automatically • UTC+1, 11:59 PM, 31 Dec → Timezone with date - Next occurrence of Dec 31 • 2025-09-21T15:30:00+02:00 → RFC3339 with timezone offset Note: If no timezone is specified, UTC is assumed. Dates without times default to midnight UTC.
Include deleted tasks in results. Defaults to false.
Only include tasks completed on or before this date. Google Tasks API requires dates in RFC3339 format (e.g., 2025-09-22T13:48:27Z). We automatically convert various human-readable formats to RFC3339: Accepted formats: • 2025-09-28T23:59:00Z → RFC3339/ISO-8601 format (preferred) - September 28, 2025 at 11:59 PM UTC • 28 Sep 2025 → Simple date format - Will be converted to midnight UTC on that date • 11:59 PM, 22 Sep 2025 → Time with date - Assumes UTC timezone if not specified • 1:00 PM, 21 Sep 2025 → 12-hour format with date - Converted to 13:00 UTC • UTC-5:30, 6:50 PM → With timezone offset - Converted to UTC automatically • UTC+1, 11:59 PM, 31 Dec → Timezone with date - Next occurrence of Dec 31 • 2025-09-21T15:30:00+02:00 → RFC3339 with timezone offset Note: If no timezone is specified, UTC is assumed. Dates without times default to midnight UTC.
Only include tasks completed on or after this date. Google Tasks API requires dates in RFC3339 format (e.g., 2025-09-22T13:48:27Z). We automatically convert various human-readable formats to RFC3339: Accepted formats: • 2025-09-28T23:59:00Z → RFC3339/ISO-8601 format (preferred) - September 28, 2025 at 11:59 PM UTC • 28 Sep 2025 → Simple date format - Will be converted to midnight UTC on that date • 11:59 PM, 22 Sep 2025 → Time with date - Assumes UTC timezone if not specified • 1:00 PM, 21 Sep 2025 → 12-hour format with date - Converted to 13:00 UTC • UTC-5:30, 6:50 PM → With timezone offset - Converted to UTC automatically • UTC+1, 11:59 PM, 31 Dec → Timezone with date - Next occurrence of Dec 31 • 2025-09-21T15:30:00+02:00 → RFC3339 with timezone offset Note: If no timezone is specified, UTC is assumed. Dates without times default to midnight UTC.
Include tasks assigned to the current user in results. Defaults to false.
Include completed tasks in results. Defaults to true.
Hard limit on total number of tasks returned across all lists to prevent large payloads. Defaults to 1000.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_LIST_TASK_LISTSFetches the authenticated user's task lists from Google Tasks; results may be paginated. Response contains task lists under the `items` key. Multiple lists may share similar names — confirm the correct list by ID before passing to other tools.
Input parameters
Token for the page of results to return; omit for the first page, use `nextPageToken` from a previous response for subsequent pages.
Maximum number of task lists to return per page. Capped at 100; values above 100 are silently truncated to 100.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_LIST_TASKSRetrieves tasks from a Google Tasks list; all date/time strings must be RFC3339 UTC, and `showCompleted` must be true if `completedMin` or `completedMax` are specified. Response key for tasks is `tasks` (not `items`). No full-text search; filter client-side by title/notes. Results ordered by position, not by date.
Input parameters
Exclude tasks due after this date. Google Tasks API requires dates in RFC3339 format (e.g., 2025-09-22T13:48:27Z). We automatically convert various human-readable formats to RFC3339: Accepted formats: • 2025-09-28T23:59:00Z → RFC3339/ISO-8601 format (preferred) - September 28, 2025 at 11:59 PM UTC • 28 Sep 2025 → Simple date format - Will be converted to midnight UTC on that date • 11:59 PM, 22 Sep 2025 → Time with date - Assumes UTC timezone if not specified • 1:00 PM, 21 Sep 2025 → 12-hour format with date - Converted to 13:00 UTC • UTC-5:30, 6:50 PM → With timezone offset - Converted to UTC automatically • UTC+1, 11:59 PM, 31 Dec → Timezone with date - Next occurrence of Dec 31 • 2025-09-21T15:30:00+02:00 → RFC3339 with timezone offset Note: If no timezone is specified, UTC is assumed. Dates without times default to midnight UTC.
Exclude tasks due before this date. Google Tasks API requires dates in RFC3339 format (e.g., 2025-09-22T13:48:27Z). We automatically convert various human-readable formats to RFC3339: Accepted formats: • 2025-09-28T23:59:00Z → RFC3339/ISO-8601 format (preferred) - September 28, 2025 at 11:59 PM UTC • 28 Sep 2025 → Simple date format - Will be converted to midnight UTC on that date • 11:59 PM, 22 Sep 2025 → Time with date - Assumes UTC timezone if not specified • 1:00 PM, 21 Sep 2025 → 12-hour format with date - Converted to 13:00 UTC • UTC-5:30, 6:50 PM → With timezone offset - Converted to UTC automatically • UTC+1, 11:59 PM, 31 Dec → Timezone with date - Next occurrence of Dec 31 • 2025-09-21T15:30:00+02:00 → RFC3339 with timezone offset Note: If no timezone is specified, UTC is assumed. Dates without times default to midnight UTC.
Token from a previous list operation for fetching a specific page; if omitted, retrieves the first page.
Maximum number of tasks to return. API default: 20, maximum: 100. Use `nextPageToken` from the response in successive calls until absent to avoid missing tasks beyond the first page.
Include hidden tasks. Defaults to false.
Identifier of the task list. IMPORTANT: For the user's primary/default task list, you MUST use the literal string '@default' (NOT 'primary', 'default', or any other variation). The value 'primary' is NOT valid and will be rejected by the API. Either use '@default' for the primary list or provide a valid task list ID obtained from list_task_lists.
Lower bound for task's last modification time (for syncing). Google Tasks API requires dates in RFC3339 format (e.g., 2025-09-22T13:48:27Z). We automatically convert various human-readable formats to RFC3339: Accepted formats: • 2025-09-28T23:59:00Z → RFC3339/ISO-8601 format (preferred) - September 28, 2025 at 11:59 PM UTC • 28 Sep 2025 → Simple date format - Will be converted to midnight UTC on that date • 11:59 PM, 22 Sep 2025 → Time with date - Assumes UTC timezone if not specified • 1:00 PM, 21 Sep 2025 → 12-hour format with date - Converted to 13:00 UTC • UTC-5:30, 6:50 PM → With timezone offset - Converted to UTC automatically • UTC+1, 11:59 PM, 31 Dec → Timezone with date - Next occurrence of Dec 31 • 2025-09-21T15:30:00+02:00 → RFC3339 with timezone offset Note: If no timezone is specified, UTC is assumed. Dates without times default to midnight UTC.
Include deleted tasks. Defaults to false.
Exclude tasks completed after this date. Google Tasks API requires dates in RFC3339 format (e.g., 2025-09-22T13:48:27Z). We automatically convert various human-readable formats to RFC3339: Accepted formats: • 2025-09-28T23:59:00Z → RFC3339/ISO-8601 format (preferred) - September 28, 2025 at 11:59 PM UTC • 28 Sep 2025 → Simple date format - Will be converted to midnight UTC on that date • 11:59 PM, 22 Sep 2025 → Time with date - Assumes UTC timezone if not specified • 1:00 PM, 21 Sep 2025 → 12-hour format with date - Converted to 13:00 UTC • UTC-5:30, 6:50 PM → With timezone offset - Converted to UTC automatically • UTC+1, 11:59 PM, 31 Dec → Timezone with date - Next occurrence of Dec 31 • 2025-09-21T15:30:00+02:00 → RFC3339 with timezone offset Note: If no timezone is specified, UTC is assumed. Dates without times default to midnight UTC.
Exclude tasks completed before this date. Google Tasks API requires dates in RFC3339 format (e.g., 2025-09-22T13:48:27Z). We automatically convert various human-readable formats to RFC3339: Accepted formats: • 2025-09-28T23:59:00Z → RFC3339/ISO-8601 format (preferred) - September 28, 2025 at 11:59 PM UTC • 28 Sep 2025 → Simple date format - Will be converted to midnight UTC on that date • 11:59 PM, 22 Sep 2025 → Time with date - Assumes UTC timezone if not specified • 1:00 PM, 21 Sep 2025 → 12-hour format with date - Converted to 13:00 UTC • UTC-5:30, 6:50 PM → With timezone offset - Converted to UTC automatically • UTC+1, 11:59 PM, 31 Dec → Timezone with date - Next occurrence of Dec 31 • 2025-09-21T15:30:00+02:00 → RFC3339 with timezone offset Note: If no timezone is specified, UTC is assumed. Dates without times default to midnight UTC.
Include completed tasks. Defaults to true. (See action docstring for interaction with `completedMin`/`Max`).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_MOVE_TASKMoves the specified task to another position in the task list or to a different task list. Use cases: - Reorder tasks within a list (use 'previous' parameter) - Create subtasks by moving a task under a parent (use 'parent' parameter) - Move tasks between different task lists (use 'destinationTasklist' parameter) - Move a subtask back to top-level (omit 'parent' parameter)
Input parameters
Task identifier of the task to move. Must be a valid task ID from the source tasklist. Obtain this from 'List Tasks' or 'Insert Task' actions.
New parent task identifier. If provided, the task becomes a subtask of this parent. The parent must exist in the destination list (or source list if no destinationTasklist is specified). Omit to move task to top level.
New previous sibling task identifier. The task will be positioned immediately after this sibling. Omit to position the task first among its siblings. Must exist in the same list as the task's destination (destinationTasklist if specified, otherwise source tasklist). Cross-list sibling references are unsupported.
Source task list identifier where the task currently exists. Use '@default' for the user's primary task list, or provide a specific task list ID obtained from 'List Task Lists'. The task must exist in this list.
Destination task list identifier. If set, the task is moved from the source tasklist to this list. Omit to reorder within the same list. Note: Recurrent tasks cannot be moved between lists.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_PATCH_TASKPartially updates an existing task (identified by `task_id`) within a specific Google Task list (identified by `tasklist_id`), modifying only the provided attributes from `TaskInput` (e.g., `title`, `notes`, `due` date, `status`) and requiring both the task and list to exist.
Input parameters
Unique identifier for the task. Generated by Google Tasks API when creating a task. Used for updating or deleting existing tasks.
Due date for the task (optional). NOTE: Google Tasks only stores the date portion (YYYY-MM-DD) - any time component provided will be automatically stripped before sending to the API. Accepts RFC3339 format (e.g., '2025-09-28T23:59:00Z') or various human-readable formats like '28 Sep 2025', '11:59 PM, 22 Sep 2025'. Normalized to midnight UTC — naive local dates without timezone offset may shift ±1 day. Time-based reminders are not supported via this field.
ETag of the resource for concurrency control. Prevents accidental overwrites when multiple clients modify the same task. Auto-generated by the API.
Additional details or description for the task. Supports plain text only (no HTML/markdown). Maximum 8192 characters. Example: 'Include Q3 sales data and projections'
Title/name of the task. This is the main text displayed for the task. Maximum 1024 characters. Example: 'Complete quarterly report'
Whether the task is hidden from the default view. Hidden tasks can still be accessed via API but won't show in UI. Default: false
Current status of the task. Must be either 'needsAction' (task is pending) or 'completed' (task is done).
Whether the task has been deleted. Deleted tasks are marked but not immediately removed, allowing for recovery. Default: false
Identifier of the Google Task to be updated within the specified task list.
Date/time when the task was marked as completed. Only applicable when status='completed'. Unlike 'due', this field preserves the time component. Accepts RFC3339 format or human-readable date formats. Malformed or non-RFC3339 values will be rejected.
Identifier of the Google Task list that contains the task to be updated.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_PATCH_TASK_LISTUpdates the title of an existing Google Tasks task list.
Input parameters
The unique identifier of the task list to be updated.
The new title for the task list. Optional for PATCH semantics - only include if you want to update the title. Maximum length: 1024 characters.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_UPDATE_TASKDEPRECATED: Use GOOGLETASKS_PATCH_TASK instead. Full-update (PUT-style) operation that overwrites unspecified fields with empty/default values, which can cause data loss. Prefer GOOGLETASKS_PATCH_TASK unless a complete field replacement is explicitly required.
Input parameters
Due date of the task (RFC 3339 timestamp).
Notes describing the task.
Title of the task.
Status of the task. Valid values: "needsAction" or "completed". When setting to "completed", the completion date will be auto-set to the current time if not explicitly provided via the completed field.
Task identifier.
Completion date of the task (RFC 3339 timestamp).
Task list identifier.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_UPDATE_TASK_FULLTool to fully replace an existing Google Task using PUT method. Use when you need to update the entire task resource, not just specific fields. This method requires all required fields (id, title) and replaces the complete task, unlike PATCH which supports partial updates.
Input parameters
Task identifier (REQUIRED). Must match the task_id parameter. This field is required by the Google Tasks API for PUT operations.
Due date for the task. NOTE: Google Tasks only stores the date portion (YYYY-MM-DD). Accepts RFC3339 format (e.g., '2025-09-28T00:00:00Z') or date strings like '2025-09-28'.
ETag of the resource for concurrency control. Prevents accidental overwrites when multiple clients modify the same task.
Collection of links attached to the task. This collection is read-only.
Additional details or description for the task. Supports plain text only. Maximum 8192 characters.
Title/name of the task (REQUIRED). This is the main text displayed for the task. Maximum 1024 characters.
Whether the task is hidden. This is read-only and set by the API when task list is cleared. Default: false
Parent task identifier for subtasks. This field is read-only. Use the 'move' method to change parent.
Current status of the task. Must be either 'needsAction' (task is pending) or 'completed' (task is done).
Whether the task has been deleted. Deleted tasks are marked but not immediately removed. Default: false
Identifier of the Google Task to be fully replaced within the specified task list. This must also be included in the 'id' field of the request body.
Position of the task among siblings. This field is read-only. Use the 'move' method to change position.
Date/time when the task was marked as completed. Only applicable when status='completed'. Unlike 'due', this field preserves the time component. Accepts RFC3339 format.
Identifier of the Google Task list that contains the task to be updated.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GOOGLETASKS_UPDATE_TASK_LISTUpdates the authenticated user's specified task list.
Input parameters
Title of the task list. Maximum length allowed: 1024 characters.
Task list identifier.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 61 agents privately built on Nagent that already use Google Tasks.
Build on Nagent
Connect Google Tasks to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Google Tasks, and click "Connect Now." You'll authenticate with OAuth — Nagent handles credential storage and refresh automatically. Once connected, Google Tasks is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Google Tasks is connected, you configure its 18 actions and 5 triggers directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Google Tasks steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Google Tasks event fires, the agent kicks off automatically.
Every Google Tasks action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Google Tasks ships with 18 pre-built task management actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Google Tasks together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Google Tasks-based workflows tailored to your business.