--- title: "Connect Google Tasks to DistrictAPI - APIANT.ai" description: "When \"New Task Created\" fires in Google Tasks, your agent runs \"Batch lookup districts\" in DistrictAPI." canonical: "https://apiant.ai/connect/google-tasks-to-districtapi" --- # Connect Google Tasks to DistrictAPI When **New Task Created** fires in [Google Tasks](https://apiant.ai/connections/google-tasks), your agent runs **Batch lookup districts** in [DistrictAPI](https://apiant.ai/connections/districtapi). Describe the whole flow and it is built, tested on every scenario and kept running. Google Tasks **5** triggers Google Tasks **16** actions DistrictAPI **8** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Google Tasks and DistrictAPI to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What Google Tasks can start in DistrictAPI - When **New Task Created** in Google Tasks then **Batch lookup districts** in DistrictAPI - When **New Task List Created** in Google Tasks then **Find districts by name, state or county** in DistrictAPI 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 DistrictAPI ## Triggers and actions 5 triggers · 24 actions - Trigger **New Task Created** Triggers when a new task is created in a Google Tasks list. Uses timestamp filtering (updatedMin) to efficiently detect new tasks. - Trigger **New Task List Created** Triggers 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 Changed** Triggers 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 Changed** Triggers 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 Updated** Triggers 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 **Batch Execute** Executes multiple Google Tasks API operations in a single HTTP batch request and returns structured per-item results. Use this to reduce LLM tool invocations when performing bulk operations like updating many tasks, moving tasks, or deleting multiple items. Note: Each sub-request still counts toward API quota; batching primarily reduces HTTP overhead and tool call count. - Action **Clear Tasks** Permanently clears all completed tasks from a specified google tasks list; this action is destructive and idempotent. - Action **Create Task List** Creates a new task list with the specified title. - Action **Delete Task** Deletes a specified task from a given task list in google tasks. - Action **Delete Task List** Permanently deletes an existing google task list, identified by `tasklist id`, along with all its tasks; this operation is irreversible. - Action **Get Task** Use to retrieve a specific google task if its `task id` and parent `tasklist id` are known. - Action **Get Task List** Retrieves a specific task list from the user's google tasks if the `tasklist id` exists for the authenticated user. - Action **Insert Task** 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. - Action **List Task Lists** Fetches the authenticated user's task lists from google tasks; results may be paginated. - Action **List Tasks** 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. - Action **Move Task** Moves the specified task to another position in the destination task list. - Action **Patch Task** 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. - Action **Patch Task List** Updates the title of an existing google tasks task list. - Action **Update Task** Updates the specified task. - Action **Update Task Full** Tool to fully replace an existing Google Task using PUT method. Use when you need to update the entire task resource, not just specific fields. This method requires all required fields (id, title) and replaces the complete task, unlike PATCH which supports partial updates. - Action **Update Task List** Updates the authenticated user's specified task list. - Action **Batch lookup districts** Looks up several school districts at once by their NCES LEA IDs and returns the full district profile for each one. - Action **Find districts by name, state or county** Returns the school districts matching the name, state or county you supply. - Action **Get district** Returns the full profile of one school district, including its address, grades served, enrollment, finances and boundary. - Action **Get school** Returns the full profile of one school, including its address, grades served, enrollment and parent district. - Action **Get school's district** Returns the full profile of the school district a given school belongs to. - Action **List districts** Returns the school districts serving a street address, a pair of coordinates, or a given NCES LEA ID. - Action **List schools** Returns the schools near a street address or a pair of coordinates, within the radius you choose. - Action **List schools by district** Returns the open schools inside a given school district, optionally limited to one school type or to charter schools. ## Each app on its own - [ **Google Tasks** Google Tasks provides a simple to-do list and task management system integrated into Gmail and Google...](https://apiant.ai/connections/google-tasks) - [ **DistrictAPI** US school districts and schools by address, with enrollment and boundaries](https://apiant.ai/connections/districtapi) Reviews ## What our customers say ## More from Google Tasks - [ **Google Tasks to BigML** BigML is a machine learning platform for building, evaluating, and running predictive models.](https://apiant.ai/connect/google-tasks-to-bigml) - [ **Google Tasks to Grist** Grist combines the flexibility of a spreadsheet with the robustness of a database to organize your data...](https://apiant.ai/connect/google-tasks-to-grist) - [ **Google Tasks to Mistral AI** Mistral AI is a platform for building, customizing, and deploying advanced AI models and agents for...](https://apiant.ai/connect/google-tasks-to-mistral-ai) - [ **Google Tasks to Morgen** Morgen is an all-in-one app for your time management](https://apiant.ai/connect/google-tasks-to-morgen) - [ **Google Tasks to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/google-tasks-to-hubspot) - [ **Google Tasks to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/google-tasks-to-salesforce) ## More into DistrictAPI - [ **Arxiv to DistrictAPI** Open-access repository API for searching and retrieving scholarly preprints in physics, math, CS, and...](https://apiant.ai/connect/arxiv-to-districtapi) - [ **HubSpot to DistrictAPI** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-districtapi) - [ **Salesforce to DistrictAPI** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-districtapi) - [ **Slack to DistrictAPI** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-districtapi) - [ **Google Sheets to DistrictAPI** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-districtapi) - [ **Gmail to DistrictAPI** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-districtapi) Questions ## Google Tasks and DistrictAPI, 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 DistrictAPI when something happens in Google Tasks? Any of DistrictAPI's 8 actions, including Batch lookup districts, Find districts by name, state or county, Get district and Get school. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from DistrictAPI to Google Tasks? DistrictAPI has no triggers in the catalog today, so automations start in Google Tasks. If you need the other direction, ask: your agent reads DistrictAPI's API documentation and adds it. ### ### Do I have to build a connector for Google Tasks or DistrictAPI? 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. ### ### Can my AI client use Google Tasks and DistrictAPI without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### 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.