Google Tasks
for LuumenAI
Read your task lists for context, add and update tasks as approved steps
Connect Google Tasks and Luumen can read the lists your team already keeps — handover items, follow-ups after an incident, small pieces of work that never make it into a ticket. It answers questions about what is open and who it sits with right away. Creating tasks, moving them between lists, or editing them goes through an approval step first.
The Google Tasks toolbox
16 tools: 5 read, 11 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet TaskRetrieve a specific Google Task.
- ReadGet task listRetrieves a specific task list from the user's Google Tasks if the `tasklist_id` exists for the authenticated user.
- ReadList All Tasks Across All ListsList all tasks across all of the user's task lists with optional filters.
- ReadList task listsFetches the authenticated user's task lists from Google Tasks; results may be paginated.
- ReadList 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.
- WriteBatch Execute Google Tasks OperationsExecutes multiple Google Tasks API operations in a single HTTP batch request and returns structured per-item results. Approval by default
- WriteClear tasksPermanently and irreversibly clears all completed tasks from a specified Google Tasks list; this action is destructive, idempotent, and cannot be undone. Approval by default
- WriteCreate a task listCreates a new task list with the specified title and returns a tasklist_id. Approval by default
- WriteDelete taskDeletes a specified task from a Google Tasks list. Approval by default
- WriteDelete task listPermanently deletes an existing Google Task list, identified by `tasklist_id`, along with all its tasks; this operation is irreversible. Approval by default
- WriteInsert 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… Approval by default
- WriteMove TaskMoves the specified task to another position in the task list or to a different task list. Approval by default
- WritePatch 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`… Approval by default
- WritePatch task listUpdates the title of an existing Google Tasks task list. Approval by default
- WriteUpdate Task (Full Replacement)Fully replace an existing Google Task using PUT method. Approval by default
- WriteUpdate Task ListUpdates the authenticated user's specified task list. Approval by default
One prompt, start to finish
What a governed Google Tasks run looks like inside Luumen.
Questions
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — batch execute google tasks operations, clear tasks, create a task list, delete task, and more — is shown as a plan and requires approval by default, including the 4 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Google Tasks — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Put Google Tasks to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.