Googletasks Automation

---
name: googletasks-automation
description: "Automate Google Tasks via Rube MCP (Composio): create, list, update, delete, move, and bulk-insert tasks and task lists. Always search tools first for current schemas."
requires:
  mcp: [rube]
executor: HYBRID
skill_id: integrations.composio.googletasks-automation
status: ADOPTED
security: {level: standard, pii: false, approval_required: false}
extends: integrations.composio.meta
toolkit: googletasks-automation
# Phase3: This stub routes to the meta-skill. See skills/integrations/composio/SKILL.md for full protocol.
anchors:
  - automation
  - integration
  - api
  - workflow
tier: 3
input_schema:
  - name: code_or_task
    type: string
    description: "Code snippet, script, or task description to process"
    required: true
output_schema:
  - name: result
    type: object
    description: "Result from the automated action"
  - name: status
    type: string
    description: "Execution status: success | partial | failure"
what_if_fails: >
  FALLBACK: If Googletasks Automation cannot complete, provide partial results with
  explicit gaps noted. Never block workflow silently.
  ESCALATE: If core capability is unavailable, suggest nearest alternative skill.
  RULE: Always explain what failed and what manual steps can substitute.
---

# Google Tasks Automation via Rube MCP

Create, manage, organize, and bulk-operate on Google Tasks and task lists using Rube MCP (Composio).

**Toolkit docs**: [composio.dev/toolkits/googletasks](https://composio.dev/toolkits/googletasks)

## Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googletasks`
- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas

## Setup
**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googletasks`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Core Workflows

### 1. List All Task Lists
Use `GOOGLETASKS_LIST_TASK_LISTS` to fetch all available task lists for the authenticated user.
```
Tool: GOOGLETASKS_LIST_TASK_LISTS
Parameters:
  - maxResults: Maximum task lists to return
  - pageToken: Pagination token for next page
```

### 2. Create a New Task
Use `GOOGLETASKS_INSERT_TASK` to add a new task to a specific task list.
```
Tool: GOOGLETASKS_INSERT_TASK
Parameters:
  - tasklist_id (required): ID of the target task list
  - title (required): Task title
  - notes: Task description/notes
  - due: Due date in RFC3339 format (e.g., "2025-01-20T00:00:00.000Z")
  - status: "needsAction" or "completed"
  - task_parent: Parent task ID (to create subtask)
  - task_previous: Previous task ID (for ordering)
```

### 3. List All Tasks Across Lists
Use `GOOGLETASKS_LIST_ALL_TASKS` to fetch tasks across all task lists with optional filters.
```
Tool: GOOGLETASKS_LIST_ALL_TASKS
Parameters:
  - max_tasks_total: Maximum total tasks to return
  - showCompleted: Include completed tasks
  - showDeleted: Include deleted tasks
  - showHidden: Include hidden tasks
  - dueMin / dueMax: Filter by due date range
  - completedMin / completedMax: Filter by completion date
  - updatedMin: Filter by last update time
  - showAssigned: Include assigned tasks
```

### 4. Update an Existing Task
Use `GOOGLETASKS_UPDATE_TASK` to modify a task's title, notes, due date, or status.
```
Tool: GOOGLETASKS_UPDATE_TASK
Parameters:
  - tasklist_id (required): Task list ID
  - task_id (required): Task ID to update
  - title: New title
  - notes: Updated notes
  - due: New due date (RFC3339)
  - status: "needsAction" or "completed"
```

### 5. Bulk Insert Tasks
Use `GOOGLETASKS_BULK_INSERT_TASKS` to create multiple tasks at once in a single operation.
```
Tool: GOOGLETASKS_BULK_INSERT_TASKS
Parameters:
  - tasklist_id (required): Target task list ID
  - tasks (required): Array of task objects (each with title, notes, due, status)
  - batch_size: Number of tasks per batch request
```

### 6. Delete or Clear Tasks
Use `GOOGLETASKS_DELETE_TASK` to remove a specific task, or `GOOGLETASKS_CLEAR_TASKS` to permanently remove all completed tasks from a list.
```
Tool: GOOGLETASKS_DELETE_TASK
Parameters:
  - tasklist_id (required): Task list ID
  - task_id (required): Task ID to delete

Tool: GOOGLETASKS_CLEAR_TASKS
Parameters:
  - tasklist (required): Task list ID to clear completed tasks from
```

## Common Patterns

- **Get task list ID first**: Always start with `GOOGLETASKS_LIST_TASK_LISTS` to discover available task lists and their IDs before creating or listing tasks.
- **List then update**: Use `GOOGLETASKS_LIST_ALL_TASKS` or `GOOGLETASKS_LIST_TASKS` to find task IDs, then use `GOOGLETASKS_UPDATE_TASK` to modify them.
- **Mark complete**: Update a task with `status: "completed"` using `GOOGLETASKS_UPDATE_TASK`.
- **Create subtasks**: Use `GOOGLETASKS_INSERT_TASK` with the `task_parent` parameter set to the parent task's ID.
- **Reorder tasks**: Use `GOOGLETASKS_MOVE_TASK` to change a task's position within its list or reparent it.
- **Batch creation**: Use `GOOGLETASKS_BULK_INSERT_TASKS` for creating many tasks at once (e.g., importing from another system).

## Known Pitfalls

- Both `tasklist_id` and `task_id` are **required** for `GOOGLETASKS_UPDATE_TASK`, `GOOGLETASKS_DELETE_TASK`, and `GOOGLETASKS_GET_TASK`. You cannot operate on a task without knowing which list it belongs to.
- All date/time strings must be in **RFC3339 format** (e.g., `2025-01-20T00:00:00.000Z`). Other formats will be rejected.
- `GOOGLETASKS_CLEAR_TASKS` permanently deletes all **completed** tasks from a list. This action is irreversible.
- `GOOGLETASKS_LIST_ALL_TASKS` fetches across all lists but results may be paginated -- check for pagination tokens.
- Task list IDs are not the same as task list names. Always resolve names to IDs using `GOOGLETASKS_LIST_TASK_LISTS`.
- The default task list is typically named "My Tasks" but its ID is an opaque string, not "default" or "primary".

## Quick Reference
| Action | Tool | Key Parameters |
|--------|------|----------------|
| List task lists | `GOOGLETASKS_LIST_TASK_LISTS` | `maxResults`, `pageToken` |
| List all tasks | `GOOGLETASKS_LIST_ALL_TASKS` | `max_tasks_total`, `showCompleted`, `dueMin` |
| List tasks in a list | `GOOGLETASKS_LIST_TASKS` | `tasklist_id`, `maxResults`, `showCompleted` |
| Get single task | `GOOGLETASKS_GET_TASK` | `tasklist_id`, `task_id` |
| Create task | `GOOGLETASKS_INSERT_TASK` | `tasklist_id`, `title`, `notes`, `due` |
| Bulk create tasks | `GOOGLETASKS_BULK_INSERT_TASKS` | `tasklist_id`, `tasks` |
| Update task | `GOOGLETASKS_UPDATE_TASK` | `tasklist_id`, `task_id`, `title`, `status` |
| Delete task | `GOOGLETASKS_DELETE_TASK` | `tasklist_id`, `task_id` |
| Move/reorder task | `GOOGLETASKS_MOVE_TASK` | `tasklist_id`, `task_id` |
| Clear completed | `GOOGLETASKS_CLEAR_TASKS` | `tasklist` |

---
*Powered by [Composio](https://composio.dev)*

## Why This Skill Exists
Stub for the `googletasks-automation` toolkit in the Composio integration ecosystem.
Extends `integrations.composio.meta` — see the meta-skill for full protocol.

## When to Use
Use when automating `googletasks-automation` tasks via Rube MCP (Composio).
For generic Composio queries, use `integrations.composio.meta` directly.

## What If Fails
See `skills/integrations/composio/SKILL.md` (meta-skill) for full fallback protocol.
RULE: Never block workflow — always suggest manual alternative if automation fails.