# Reply to Side Conversation — Zendesk

> Reply to an existing Zendesk side conversation. Zendesk requires recipients on every reply, so pass the participants the reply should go to. See the documentation

- Key: `zendesk-reply-to-side-conversation`
- Type: Action (Write)
- Version: 0.0.2
- App: Zendesk (`zendesk`) — https://pipedream.com/apps/zendesk.md
- This page (HTML): https://pipedream.com/apps/zendesk/actions/reply-to-side-conversation
- Hints: open-world
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/zendesk/actions/reply-to-side-conversation/reply-to-side-conversation.mjs

## Description

Reply to an existing Zendesk side conversation. Zendesk requires recipients on every reply, so pass the participants the reply should go to. [See the documentation](https://developer.zendesk.com/api-reference/ticketing/side_conversation/side_conversation/#reply-to-side-conversation)

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `ticketId` | `string` | Yes | The ID of the ticket. Options are loaded from the connected account. |
| `sideConversationId` | `string` | Yes | Identifier of the side conversation (UUID, e.g. 8566255a-ece5-11e8-857d-493066fa7b17). Select List Side Conversations to see available IDs for a ticket. Options are loaded from the connected account. |
| `body` | `string` | Yes | The plain-text body of the side conversation message. |
| `recipients` | `string` | Yes | Recipients for this reply, as a JSON array of participant objects. Zendesk requires this on every reply, and returns Invalid parameter: to is required when it is omitted, so repeat the participants the reply should go to (read them with Get Side Conversation). Use [{"email":"person@example.com","name":"Person"}] for an external email recipient or [{"user_id":123}] for an existing Zendesk agent. Do not mix participant types in the same array. |
| `subject` | `string` | No | The subject of the side conversation message. |
| `customSubdomain` | `string` | No | For Enterprise Zendesk accounts: optionally specify the subdomain to use. This will override the subdomain that was provided when connecting your Zendesk account to Pipedream. For example, if you Zendesk URL is https://examplehelp.zendesk.com, your subdomain is examplehelp |

## Run it

**MCP**

```ts
import { Client } from "@modelcontextprotocol/sdk/client/index.js"
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"
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 accessToken = await pd.rawAccessToken

const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": process.env.PIPEDREAM_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": "zendesk",
      },
    },
  },
)

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: "zendesk-reply-to-side-conversation",
  arguments: {
    ticketId: "Ticket ID",
    sideConversationId: "Side Conversation ID",
  },
})
```

**TypeScript**

```ts
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: "zendesk-reply-to-side-conversation",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    zendesk: { authProvisionId: "apn_xxxxxxx" },
    ticketId: "Ticket ID",
    sideConversationId: "Side Conversation ID",
  },
})

console.log(result)
```

**cURL**

```bash
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": "zendesk-reply-to-side-conversation",
    "configured_props": {
      "zendesk": { "authProvisionId": "apn_xxxxxxx" },
      "ticketId": "Ticket ID",
      "sideConversationId": "Side Conversation ID"
    }
  }'
```

---

- App: https://pipedream.com/apps/zendesk.md · All apps: https://pipedream.com/apps