View as Markdown
Teamwork Desk icon

Teamwork Desk ACTION

Reply To Ticket

Reply to a specific ticket See the documentation
  • Action
  • Writes data
  • OAuth
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Teamwork Desk account once, then configure and run Reply To 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-reply-to-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)

SCHEMA

Inputs

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

Reply To Ticket inputs
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
statusId Status Id string
The Id of the status.
Required Dynamic
threadType Thread Type string
The type of the thread
Required
message Message string
The ticket's initial message.
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
teamwork_desk-reply-to-ticket
Version
0.0.3
App
Teamwork Desk
Authentication
OAuth
Read-only
No
Destructive
No
Open world
Yes