Files and knowledge
Google Tasks for AI agents.
Managed auth, ready-made tools.
Create, update, complete and review to-dos in Google Tasks on behalf of each of your users.
About Google Tasks
With the Google Tasks connector, your agent manages to-dos in each user’s own Google Tasks. It can list their task lists and tasks, add new tasks with due dates, update them, mark them done or delete them, using only the tools your project allows.
Google Tasks is Google’s to-do list, built into Gmail, Calendar and its own app.
Tools
What your agent can do in Google Tasks.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Google Tasks connection.
-
List task lists
Readgoogle_tasks_list_tasklistsList the user's task lists.
-
List tasks
Readgoogle_tasks_list_tasksList the tasks in a task list.
-
Create a task
Writegoogle_tasks_create_taskAdd a task with an optional due date and notes.
-
Update a task
Writegoogle_tasks_update_taskChange a task's title, notes or due date.
-
Complete a task
Writegoogle_tasks_complete_taskMark a task as completed.
-
Delete a task
Writegoogle_tasks_delete_taskRemove a task from a list.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Google Tasks, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read and add tasks, and switch off
google_tasks_delete_taskso it can never remove one. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example reading tasks but not changing them. A call outside them is refused.
Get started
Connect Google Tasks
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Google Tasks
Each end user authorizes their own Google Tasks account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Google Tasks account, once. const connection = await agent200 .user("user_123") .connect("google_tasks"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Google Tasks tools
Name the user, the model and the tools. The model decides which Google Tasks tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Add a task to renew the domain by Friday", tools: ["google_tasks"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Google's own sign-in page. You never see or store their Google password.
-
What access is requested
The scopes the connection needs, such as viewing tasks or managing tasks, listed on Google's authorization screen. Users can remove the app later from their Google Account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Google Tasks connector and how to use it.
Connector: Google Tasks, through Agent200. In code: "google_tasks". What it does: Create, update, complete and review to-dos in Google Tasks on behalf of each of your users. Page: https://www.agent200.com/connectors/google-tasks/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Google Tasks's own page, through the authorization link Agent200 returns. Never ask a user for a Google Tasks password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: google_tasks_list_tasklists, google_tasks_list_tasks. Write tools: google_tasks_create_task, google_tasks_update_task, google_tasks_complete_task, google_tasks_delete_task. Name "google_tasks" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/google-tasks/framework/claude/ https://www.agent200.com/connectors/google-tasks/framework/chatgpt/ https://www.agent200.com/connectors/google-tasks/framework/claude-code/ https://www.agent200.com/connectors/google-tasks/framework/muse/ https://www.agent200.com/connectors/google-tasks/framework/grok-bot/ https://www.agent200.com/connectors/google-tasks/framework/openai-dots/ https://www.agent200.com/connectors/google-tasks/framework/claude-duet/ https://www.agent200.com/connectors/google-tasks/framework/hermes-agent/ https://www.agent200.com/connectors/google-tasks/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/google-tasks.md
Guides
Use Google Tasks with the AI you build on.
Step-by-step setup for Google Tasks with a specific model, assistant or agent framework.
-
Google Tasks + Claude
How to connect Google Tasks to Claude
-
Google Tasks + ChatGPT
How to connect Google Tasks to ChatGPT
-
Google Tasks + Claude Code
How to connect Google Tasks to Claude Code
-
Google Tasks + Muse
How to connect Google Tasks to Muse
-
Google Tasks + Grok Bot
How to connect Google Tasks to Grok Bot
-
Google Tasks + OpenAI Dots
How to connect Google Tasks to OpenAI Dots
-
Google Tasks + Claude Duet
How to connect Google Tasks to Claude Duet
-
Google Tasks + Hermes Agent
How to connect Google Tasks to Hermes Agent
-
Google Tasks + OpenClaw
How to connect Google Tasks to OpenClaw
FAQ
Google Tasks and Agent200, answered.
Who handles the Google Tasks OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Google Tasks.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Google Tasks connection, never another user's. It cannot reach anything the user or Google Tasks has not authorized.
Can I limit what my agent can do in Google Tasks?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.