Google Tasks

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

    Read
    google_tasks_list_tasklists

    List the user's task lists.

  • List tasks

    Read
    google_tasks_list_tasks

    List the tasks in a task list.

  • Create a task

    Write
    google_tasks_create_task

    Add a task with an optional due date and notes.

  • Update a task

    Write
    google_tasks_update_task

    Change a task's title, notes or due date.

  • Complete a task

    Write
    google_tasks_complete_task

    Mark a task as completed.

  • Delete a task

    Write
    google_tasks_delete_task

    Remove a task from a list.

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_task so 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. 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.js
    Conceptual example
    Set 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. 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.js
    Conceptual example
    Let 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. 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.js
    Conceptual example
    Run 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.

Agent brief
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.

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.

  • Google Drive

    Google Drive

    Find, read and organize the files in each user's Drive.

    Managed OAuth Files and knowledge
  • OneDrive

    OneDrive

    Search, read, upload and share OneDrive files, including Word, Excel and PowerPoint documents, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Dropbox

    Dropbox

    Search, read, upload and organize Dropbox files, and create shared links, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Notion

    Notion

    Search, read and write Notion pages and databases on behalf of each of your users.

    Managed OAuth Files and knowledge
200 OK

Start with Google Tasks.
Your agent does the rest.

Your users connect their own Google Tasks accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)