Google Tasks ACTION
Move Task
Moves an existing task to a different position, parent task, or task list. Use this action to reorganize your task hierarchy or reorder tasks without modifying the task's title, notes, due date, or completion status. To update those properties, use the Update Task action instead. See the documentation
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Google Tasks account once, then configure and run Move Task from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "google_tasks-move-task",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
google_tasks: { authProvisionId: "apn_xxxxxxx" },
taskListId: "Task List",
taskId: "Task",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "google_tasks-move-task",
"configured_props": {
"google_tasks": { "authProvisionId": "apn_xxxxxxx" },
"taskListId": "Task List",
"taskId": "Task"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "google_tasks",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "google_tasks-move-task",
arguments: {
taskListId: "Task List",
taskId: "Task",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
taskListId Task List | string | The ID of the task list. Required Dynamic |
taskId Task | string | The ID of the task. Required Dynamic |
destinationTasklist Destination Task List | string | Optional. The ID of the destination task list (for example, MDQ5MjE4NzQ2OTM0NjYxNzA6MDow). You can obtain this ID using the List Task Lists action. If omitted, the task is moved within its current task list. Optional Dynamic |
parent Parent Task | string | Optional. The ID of the parent task under which the task will be moved (for example, MDQ5MjE4NzQ2OTM0NjYxNzA6MDow). You can obtain this ID using the List Tasks action. Optional Dynamic |
previous Place After Task | string | Optional. The ID of the sibling task after which the task should be placed (for example, MDQ5MjE4NzQ2OTM0NjYxNzA6MDox). You can obtain this ID using the List Tasks action. Optional Dynamic |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- google_tasks-move-task
- Version
- 0.0.2
- App
- Google Tasks
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗