Teamwork Desk ACTION
Update Ticket
Update a specific ticket See the documentation
- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Teamwork 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: "teamwork_desk-update-ticket",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
teamwork_desk: { authProvisionId: "apn_xxxxxxx" },
ticketId: "Ticket Id",
bcc: ["BCC"],
},
})
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": "teamwork_desk-update-ticket",
"configured_props": {
"teamwork_desk": { "authProvisionId": "apn_xxxxxxx" },
"ticketId": "Ticket Id",
"bcc": ["BCC"]
}
}'// 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": "teamwork_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: "teamwork_desk-update-ticket",
arguments: {
ticketId: "Ticket Id",
bcc: ["BCC"],
},
})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 |
|---|---|---|
ticketId Ticket Id | string | The Id of the ticket. Required Dynamic |
bcc BCC | string[] | List of BCC for the initial message. Optional |
cc CC | string[] | List of CC for the initial message. Optional |
customerId Customer | string | The customer id. Required Dynamic |
inboxId Inbox ID | string | The id of the inbox. Required Dynamic |
message Message | string | The ticket's initial message. Required |
notifyCustomer Notify Customer | boolean | Whether to notify the customer when an agent creates a ticket on behalf of the customer. Required |
priorityId Priority Id | string | The Id of the priority. Required Dynamic |
sourceId Source Id | string | The Id of the source. Required Dynamic |
statusId Status Id | string | The Id of the status. Required Dynamic |
subject Subject | string | The ticket's subject. Required |
tagIds Tags | string[] | The list of word the ticket was tagged with. Optional Dynamic |
typeId Type Id | string | The Id of the type. Required 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
- teamwork_desk-update-ticket
- Version
- 0.0.3
- App
- Teamwork Desk
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗