Zoho Desk ACTION
Update Ticket
Updates an existing ticket. See the docs here
- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Zoho Desk account once, then configure and run Update Ticket 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: "zoho_desk-update-ticket",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
zoho_desk: { authProvisionId: "apn_xxxxxxx" },
orgId: "Organization ID",
ticketId: "Ticket ID",
},
})
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": "zoho_desk-update-ticket",
"configured_props": {
"zoho_desk": { "authProvisionId": "apn_xxxxxxx" },
"orgId": "Organization ID",
"ticketId": "Ticket ID"
}
}'// 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": "zoho_desk",
},
},
},
)
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: "zoho_desk-update-ticket",
arguments: {
orgId: "Organization ID",
ticketId: "Ticket ID",
},
})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 |
|---|---|---|
orgId Organization ID | string | The ID of the organization Required Dynamic |
ticketId Ticket ID | string | The ID of the ticket Required Dynamic |
subject Subject | string | Subject of the ticket Optional |
description Description | string | Description in the ticket Optional |
status Status | string | Status of the ticket Required Dynamic |
priority Priority | string | Priority level of the ticket Optional Dynamic |
assigneeId Assignee | string | The agent assigned to the ticket Optional Dynamic |
departmentId Department ID | string | The ID of the department Required Dynamic |
contactId Contact ID | string | The ID of the contact Required Dynamic |
channel Channel | string | The channel through which the ticket was created Optional Dynamic |
classification Classification | string | Classification of the ticket Optional Dynamic |
category Category | string | Category of the ticket Optional |
subCategory Sub Category | string | Sub-category of the ticket Optional |
dueDate Due Date | string | Due date for the ticket in ISO 8601 format (e.g., 2024-12-31T23:59:59Z) Optional |
productId Product ID | string | The ID of the product Optional |
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
- zoho_desk-update-ticket
- Version
- 0.0.12
- App
- Zoho Desk
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗