Google Tasks connector for AI agents

Tools your productivity agent reaches for on Google Tasks, scoped per user.

CALL ANY TOOL

Task lists on Google Tasks: create and complete tasks, move items between lists, set due dates, and read subtask structure.

googletasks_clear_completed_tasks

Clear completed tasks

Clear all completed tasks from a task list in a connected Google Tasks account. The affected tasks are marked hidden and no longer returned by default when listing tasks. Use clear_completed_tasks to tidy up a list after finishing items. Use list_tasks with show_completed and show_hidden set to true to review cleared tasks first.

Parameters

Name

Type

Required

Description

tasklist_id

string

Required

Identifier of the task list to clear completed tasks from

schema_version

string

Optional

Optional schema version to use for tool execution

tool_version

string

Optional

Optional tool version to use for execution

googletasks_create_task

Create task

googletasks_create_tasklist

Create tasklist

googletasks_delete_task

Delete task

googletasks_delete_tasklist

Delete tasklist

googletasks_get_task

Get task

googletasks_get_tasklist

Get tasklist

googletasks_list_tasklists

List tasklists

googletasks_list_tasks

List tasks

googletasks_move_task

Move task

googletasks_update_task

Update task

googletasks_update_tasklist

Update tasklist

Build your Agent

Drop the toolkit in, point it at the user, and your productivity agent can use Google Tasks from the first run.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Google Tasks tools, scoped to the signed-in user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["googletasks"], toolNames: [
    "googletasks_clear_completed_tasks",
    "googletasks_create_task",
    "googletasks_create_tasklist"
  ] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "What is on my task list for today?" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Google Tasks tools, scoped to the signed-in user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["googletasks"], toolNames: [
    "googletasks_clear_completed_tasks",
    "googletasks_create_task",
    "googletasks_create_tasklist"
  ] },
  pageSize: 100,
});

const openai = new OpenAI();
const res = await openai.responses.create({
  model: "gpt-5",
  tools: tools.map((t) => t.openai),
  input: "What is on my task list for today?",
});

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Google Tasks tools, scoped to the signed-in user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["googletasks"], toolNames: [
    "googletasks_clear_completed_tasks",
    "googletasks_create_task",
    "googletasks_create_tasklist"
  ] },
  pageSize: 100,
});

const anthropic = new Anthropic();
const msg = await anthropic.messages.create({
  model: "claude-opus-4-6",
  max_tokens: 1024,
  tools: tools.map((t) => t.anthropic),
  messages: [{ role: "user", content: "What is on my task list for today?" }],
});

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Google Tasks tools, scoped to the signed-in user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["googletasks"], toolNames: [
    "googletasks_clear_completed_tasks",
    "googletasks_create_task",
    "googletasks_create_tasklist"
  ] },
  pageSize: 100,
});

const agent = new Agent({
  name: "googletasks_agent",
  model: "gemini-2.5-pro",
  instruction: "Act as the productivity agent for the signed-in user.",
  tools,
});
await agent.run("What is on my task list for today?");

Try these prompts

Paste any prompt into your agent to start using Google Tasks.

Daily review

Copy the prompt

Copied

What is on my task list for today?

Copy the prompt

Copied

Show overdue tasks across all my lists.

Copy the prompt

Copied

Which tasks have subtasks still open?

Capture

Copy the prompt

Copied

Add a task to follow up with Acme on Friday.

Copy the prompt

Copied

Create a list for the launch checklist and add five items.

Copy the prompt

Copied

Move the vendor review task to next Monday.

Cleanup

Copy the prompt

Copied

Mark the expense report task complete.

Copy the prompt

Copied

Delete completed tasks older than 30 days.

Copy the prompt

Copied

Which list has the most open items?

SEE HOW AUTH WORKS

Users authorize Google Tasks once. Their credentials stay vaulted, every call is checked, and every action is logged.

Authorize

Your user connects

Google Tasks

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Google Tasks

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Google Tasks

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Google Tasks

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

Same per-user auth pattern across other agents and MCP connectors. Working code, live demos, fork what fits.

Engineering Teams

Slack triage

Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.

Support and Ops Teams

Meeting prep

Pulls agenda, participant context, and open action items before every meeting.

Engineering Teams

Engineering standup agent

Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.

Engineering Teams

DevOps assistant agent

Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.

// shared token
audit → bot_service_account
user_filter → broken

// scalekit
audit → user_abc
scope → enforced ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Google Tasks today. Others tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Google Tasks as the user or as a shared key?

As the user. Each member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Google Tasks oauth 2.0 credential stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Google Tasks?

Yes. Pass a tool name filter to listScopedTools so the productivity agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Google Tasks.

What happens when a user revokes Google Tasks access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Does the agent see tasks from other people's accounts?

No. Google Tasks is per-account, and the connector calls with the authorizing user's own credential, so the agent sees exactly that person's lists. Shared calendars and delegated mailboxes do not widen task access.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit