Integration
Connect Google Tasks to Peaka
When something happens in Google Tasks, your agent does the next thing in Peaka. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Google Tasks and Peaka to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Google Tasks can start in Peaka
When New Task Created in Google Tasks
then Add connection in Peaka
When New Task List Created in Google Tasks
then Add query in Peaka
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Google Tasks and Peaka
Triggers and actions 5 triggers · 24 actions
Trigger
New Task CreatedTriggers when a new task is created in a Google Tasks list. Uses timestamp filtering (updatedMin) to efficiently detect new tasks.
Trigger
New Task List CreatedTriggers when a new Google Tasks task list is created. This trigger monitors Google Tasks and fires when new task lists are detected.
Trigger
Task Details ChangedTriggers when a specific task's details change. This trigger monitors a single Google Task and fires when any of its details (title, notes, status, due date, completion, position) are modified.
Trigger
Task List ChangedTriggers when a task list changes (title or content updates). This trigger monitors a specific Google Tasks list and fires when changes are detected.
Trigger
Task UpdatedTriggers when an existing task is updated in a Google Tasks list. This trigger monitors a specific task list and fires when tasks are modified.
Action
Clear TasksPermanently clears all completed tasks from a specified google tasks list; this action is destructive and idempotent.
Action
Create Task ListCreates a new task list with the specified title.
Action
Delete TaskDeletes a specified task from a given task list in google tasks.
Action
Delete Task ListPermanently deletes an existing google task list, identified by `tasklist id`, along with all its tasks; this operation is irreversible.
Action
Get TaskUse to retrieve a specific google task if its `task id` and parent `tasklist id` are known.
Action
Get Task ListRetrieves a specific task list from the user's google tasks if the `tasklist id` exists for the authenticated user.
Action
Insert TaskCreates 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.
Action
List Task ListsFetches the authenticated user's task lists from google tasks; results may be paginated.
Action
List TasksRetrieves 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.
Action
Move TaskMoves the specified task to another position in the destination task list.
Action
Patch TaskPartially 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.
Action
Patch Task ListUpdates the title of an existing google tasks task list.
Action
Update TaskUpdates the specified task.
Action
Update Task ListUpdates the authenticated user's specified task list.
Action
Add connectionCreates a new data source connection in a Peaka project.
Action
Add queryCreates a saved SQL query (plain or materialized) in a Peaka project, optionally inside a folder.
Action
Delete connectionDeletes a connection from a Peaka project. Any catalogs using this connection lose access to their data source.
Action
Delete queryPermanently deletes a saved query from a Peaka project.
Action
Get queryReturns a single saved query in a Peaka project by its ID, including its SQL, type, schedule and folder location.
Action
List connectionsLists all connections (authenticated links to external data sources) in a Peaka project.
Action
List projectsLists all projects within a Peaka workspace.
Action
List queriesReturns all saved queries in a Peaka project, including each query's folder path when it sits in a folder.
Action
Run Peaka Query (With Line Item Support)Runs a SQL statement, a saved query, or a query builder request in a Peaka project and returns the result rows as line items.
Action
Update queryUpdates the display name, SQL, type or schedule of an existing Peaka query. Fields left blank keep their current values.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Google Tasks
Google Tasks to BigMLBigML is a machine learning platform for building, evaluating, and running predictive models.
Google Tasks to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Google Tasks to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Tasks to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Tasks to MailchimpMailchimp marketing automation and email platform.
Google Tasks to StripeStripe is a payment processing platform for online businesses.
More into Peaka
HubSpot to PeakaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to PeakaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to PeakaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to PeakaGoogle Sheets
Gmail to PeakaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PeakaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Google Tasks and Peaka, answered
What can start an automation from Google Tasks?
Any of Google Tasks's 5 triggers in the catalog, including New Task Created, New Task List Created, Task Details Changed and Task List Changed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Peaka when something happens in Google Tasks?
Any of Peaka's 10 actions, including Update query, Add connection, Add query and Get query. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Peaka to Google Tasks?
Peaka has no triggers in the catalog today, so automations start in Google Tasks. If you need the other direction, ask: your agent reads Peaka's API documentation and adds it.
Do I have to build a connector for Google Tasks or Peaka?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.