Captures follow-ups from live conversations, reads back what is outstanding across every list, and reorganizes or clears finished work.
16actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro creates a new task in a Google Tasks list, optionally nesting it under a parent task or placing it after another one. A support agent logs a customer follow-up the moment a call ends, instead of writing it down and adding it later.
Ayro retrieves the details of a specific Google Task. An agent checks whether a follow-up is still open and what it says before reaching back out to a customer.
Ayro updates specific fields on an existing task, such as its title, notes, due date, or status, without touching the rest. A team marks a follow-up done or reschedules it in one step instead of rebuilding the whole task.
Each card is one request a support team gets, and the Google Tasks actions Ayro runs to close it.
Ayro reads the account's task lists, pulls everything open across all of them at once, and narrows to a single list with filters when the question is about one workstream.
Ayro inserts a task with its due date, optionally as a subtask under an existing item, creates a new list when the work does not belong in an existing one, and batches several inserts into one request.
Ayro patches just the fields that moved - title, notes, due date or status - replaces the whole task when it has been redefined, and reads it back to confirm.
Ayro moves a task to a different position or another list entirely, renames a list that no longer describes its contents, and clears completed items once they are done.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Google Tasks actions it has and picks the ones a request needs.
Authorize the Google Tasks account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Google Tasks actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeGoogle Tasks · Ayro
What can you do in Google Tasks without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Google Tasks.
Google Tasks scopes task IDs to their list. Get Task, Patch Task and Delete Task all require both a tasklist_id and a task_id - a task cannot be retrieved by ID alone - so Ayro resolves the list first through List Task Lists or List All Tasks Across All Lists.
All 16 actions your agent can call on Google Tasks, straight from the live MCP connection.
Executes multiple Google Tasks API operations in a single HTTP batch request and returns structured per-item results.
Permanently and irreversibly clears all completed tasks from a specified Google Tasks list; this action is destructive, idempotent, and cannot be undone.
Creates a new task list with the specified title and returns a tasklist_id.
Deletes a specified task from a Google Tasks list.
Permanently deletes an existing Google Task list, identified by tasklist_id, along with all its tasks; this operation is irreversible.
Retrieve a specific Google Task.
Retrieves a specific task list from the user's Google Tasks if the tasklist_id exists for the authenticated user.
Creates a new task in a given tasklist_id, optionally as a subtask of an existing task_parent or positioned after an existing task_previous sibling, where both task_parent and task_previous must belong to the same tasklist_id if specified.
List all tasks across all of the user's task lists with optional filters.
Fetches the authenticated user's task lists from Google Tasks; results may be paginated.
Retrieves tasks from a Google Tasks list; all date/time strings must be RFC3339 UTC, and showCompleted must be true if completedMin or completedMax are specified.
Moves the specified task to another position in the task list or to a different task list.
Partially updates an existing task (identified by task_id) within a specific Google Task list (identified by tasklist_id), modifying only the provided attributes from TaskInput (e.g., title, notes, due date, status) and requiring both the task and list to exist.
Updates the title of an existing Google Tasks task list.
Fully replace an existing Google Task using PUT method.
Updates the authenticated user's specified task list.
Same connection, same setup. Pick the next one your team already uses.
Verifies single addresses and bulk lists, screens domains and toxicity, and watches the credit balance before a run starts.
Explains why a domain was blocked and under which policy, updates allow and block lists on approval, and pulls threat and traffic reports for a network.
Reads the form catalog, question labels, submission results, and webhook configuration for any Formsite form on request.
Kicks off Manus tasks from a conversation, reports status and credit usage, and subscribes to task events without polling.
Builds and re-runs route optimizations, reports where a route and its stops stand, moves or merges destinations, and marks stops complete.
Starts browser automation runs from a plain-language goal, polls them to completion, cancels the ones that should stop, and returns step screenshots.

Authorize the account and your agent has all 16 actions from the first conversation.
