Google Tasks API

Name: Google Tasks API
Brand: Google Tasks API
Availability: InStock

✓ Official Vendor SpecProductivityTask Managementoauth214 EndpointsREST

Install Jentic One Beta

Connect the Google Tasks API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google Tasks API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Google Tasks API.

Create, update, and complete individual tasks within a user's task list

List all task lists for the authenticated user

Reorder tasks within a list using the move action

Clear all completed tasks from a list in a single call

GET STARTED

Start building with Google Tasks API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Google Tasks API for, with concrete tasks.

★ AI Assistant Task Capture

An AI assistant transcribing a meeting extracts action items and writes them straight into the user's Google Tasks list. The assistant calls insert under /tasks/v1/lists/{tasklist}/tasks for each action item with a title, due date, and notes field referencing the meeting. The user sees the captured tasks appear in Gmail, Calendar, and the Tasks mobile app within seconds.

POST /tasks/v1/lists/@default/tasks with title='Send proposal to Acme', due='2026-06-17T17:00:00Z', and notes containing the source meeting link.

Cross-Tool Task Sync

A productivity dashboard syncs tasks bidirectionally between Google Tasks and a project management tool. The integration polls /tasks/v1/lists/{tasklist}/tasks with the updatedMin parameter to retrieve recently changed tasks, then mirrors them to the other system. Completion-state changes flow through patch calls so users can mark tasks done in either tool.

GET /tasks/v1/lists/{tasklist}/tasks?updatedMin=2026-06-10T00:00:00Z and for each modified task issue a PATCH against the corresponding task in the other system.

Workspace Onboarding Task Templates

An HR onboarding workflow creates a personalised task list for each new hire on day one. The system creates a fresh task list under the new hire's account, inserts a sequence of onboarding tasks (read handbook, set up dev environment, schedule 1:1s) with due dates spread over the first two weeks, and shares progress visibility with the manager. Existing employees see their onboarding tasks in the Google Tasks side panel inside Gmail.

Create a new tasklist via POST /tasks/v1/users/@me/lists named 'Onboarding Week 1', then insert 8 child tasks under it with sequential due dates.

Agent-Maintained Daily Plan via Jentic

An AI agent acts as a personal daily planner. Each morning it lists yesterday's incomplete tasks, reschedules them with new due dates, clears completed items, and inserts new tasks based on calendar events scraped from Calendar API. Through Jentic the agent's OAuth token is held in the vault and refreshed automatically across runs.

Through Jentic, search 'add a task to google tasks', load POST /tasks/v1/lists/@default/tasks, and execute it for each action item the agent generated overnight.

Key Endpoints

14 endpoints — the google tasks api exposes the same tasks and task lists that surface inside gmail, google calendar, and the tasks mobile apps.

METHOD

PATH

DESCRIPTION

GET

/tasks/v1/users/@me/lists

List all task lists for the authenticated user

POST

/tasks/v1/users/@me/lists

Create a new task list

GET

/tasks/v1/lists/{tasklist}/tasks

List tasks within a list

POST

/tasks/v1/lists/{tasklist}/tasks

Insert a new task into a list

POST

/tasks/v1/lists/{tasklist}/tasks/{task}/move

Move a task to a new position or under a different parent

POST

/tasks/v1/lists/{tasklist}/clear

Clear all completed tasks from a list

GET

/tasks/v1/users/@me/lists

List all task lists for the authenticated user

POST

/tasks/v1/users/@me/lists

Create a new task list

GET

/tasks/v1/lists/{tasklist}/tasks

List tasks within a list

POST

/tasks/v1/lists/{tasklist}/tasks

Insert a new task into a list

POST

/tasks/v1/lists/{tasklist}/tasks/{task}/move

Move a task to a new position or under a different parent

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Google Tasks OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'add a task to google tasks' or 'list my google tasks', and Jentic returns the matching Tasks v1 operation with its input schema, including the tasklist id and task body, so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Google Tasks API through Jentic.

What authentication does the Google Tasks API use?

Google Tasks uses OAuth 2.0 with two scopes - https://www.googleapis.com/auth/tasks for full read/write and https://www.googleapis.com/auth/tasks.readonly for view-only access. Choose the readonly scope when your integration only lists tasks. Through Jentic, the OAuth tokens are stored encrypted and refresh transparently, so the agent never handles raw bearer tokens.

Can I create subtasks with the Google Tasks API?

Yes. Insert a child task with POST /tasks/v1/lists/{tasklist}/tasks and pass the parent parameter set to the parent task's ID, or use the move endpoint with parent and previous parameters to nest an existing task. The Tasks mobile app and Gmail side panel render the resulting hierarchy as nested checkboxes.

What are the rate limits for the Google Tasks API?

The default per-project quota is 50,000 queries per day with a per-user limit of approximately 5 queries per second. Tasks resources are small so most integrations stay well within the daily cap; back off on 429 responses and use the updatedMin parameter on list calls to avoid full re-syncs.

How do I add a task through Jentic?

Search Jentic for 'add a task to google tasks', load the schema for POST /tasks/v1/lists/{tasklist}/tasks, and execute it with the target tasklist ID (use '@default' for the user's primary list) plus the task title and optional due date. Get started with Jentic One, the self-hosted execution layer.

Is the Google Tasks API free?

Yes, the Google Tasks API is free to use within the standard daily quota. There is no per-call charge - it is part of the Google Workspace and consumer Google account surface, billed only as part of standard Workspace subscriptions where applicable.

Can I clear completed tasks in bulk?

Yes. POST /tasks/v1/lists/{tasklist}/clear deletes every task in the specified list whose status is 'completed' in a single call. This is the most efficient way to archive finished work; cleared tasks are not recoverable through the API so confirm intent before calling.

Can I limit what my agent is allowed to do with the Google Tasks API?

Yes. Because you run Jentic One yourself, your own rules decide which Google Tasks operations and credentials the agent may use. Since the task list lives in the URL path (/tasks/v1/lists/{tasklist}/tasks), you can pin the agent to a single list so it only reads and inserts tasks there. You choose the operations it can call, so destructive ones like clearing completed tasks or deleting a list are excluded unless you add them.

Google Tasks API

Connect the Google Tasks API to your agent

Capabilities

Start building with Google Tasks API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs