View as Markdown
Quo icon

Quo ACTION

Update Task

Update an existing task's title and description by ID. NOTE: the OpenPhone update endpoint only modifies title and description (both required on every update); due date and assignee are managed via other endpoints. Use List Tasks to find task IDs. Example: call with taskId="TK123abc", title="Follow up (urgent)", description="Customer asked about pricing tiers." → updates both fields and returns the updated task record. See the documentation
  • Action
  • Writes data
  • API key
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Quo account once, then configure and run Update 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: "openphone-update-task",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    openphone: { authProvisionId: "apn_xxxxxxx" },
    taskId: "Task ID",
    title: "Title",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

Update Task inputs
Property Type Description
taskId Task ID string
The ID of the task (format TK...). Run the List Tasks action to find task IDs.
Required
title Title string
The updated task title.
Required
description Description string
The updated task description.
Required

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
openphone-update-task
Version
0.0.2
App
Quo
Authentication
API key
Read-only
No
Destructive
No
Open world
Yes