Skip to main content
Per-app Google setup is deprecated. All Google apps now share one Google OAuth client and one Redirect URI. To use your own client, follow the Google setup guide. Credentials saved for one Google app apply to all of them.

​
Overview

OneCLI connects AI agents to Google Tasks through Google’s OAuth flow. Agents can create tasks, mark them complete, and organize them into task lists. The gateway injects OAuth credentials into requests to the Google Tasks API automatically. This is useful for agents that need to track follow-up items, create to-do lists, or manage tasks alongside Google Calendar.

​
What you will set up

  • A Google OAuth client shared by every Google app in OneCLI
  • A Google Tasks connection authorized with your account
  • Per-agent, per-tool access to your task lists

​
Connect Google Tasks

This applies on OneCLI Cloud and self-hosted alike. One Google client serves every Google app in OneCLI, so you set it up once. If you already did it for another Google app, skip to step 2.

1. Set up your Google client

Follow the Google setup guide. It enables the Google APIs, sets up the consent screen, creates the OAuth client, and adds the Redirect URI.
Open Connections > Google Tasks, select Connect Google Tasks, pick your Google account, and click Allow.
OneCLI connect window for Google Tasks showing Configuration required, the setup guide link, and the Configure credentials button.

The Google Tasks connect window before a Google client is set up.

​
What agents can do

  • List all task lists on the account
  • Create, rename, and delete task lists
  • List tasks within a task list, optionally showing completed tasks
  • Create new tasks with a title, notes, and due date
  • Update task details (title, notes, due date, status)
  • Mark tasks as completed
  • Delete tasks
  • Move tasks to change their order or parent (for sub-tasks)
  • Clear all completed tasks from a list

​
Controlling access

Access is per agent: grant the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization rules add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches Google Tasks.

​
FAQ

Yes. Follow the Google setup guide once. One client serves every Google app in OneCLI.
No. The token stays in OneCLI, and the gateway adds it at the proxy. See How it works.
Open Connections > Google Tasks and connect again. Agents with access use the new connection automatically.