# Ticket Solved (Instant) — Zendesk

> Emit new event when a ticket has changed to solved status

- Key: `zendesk-ticket-solved`
- Type: Trigger (Instant)
- Version: 0.2.19
- App: Zendesk (`zendesk`) — https://pipedream.com/apps/zendesk.md
- This page (HTML): https://pipedream.com/apps/zendesk/triggers/ticket-solved
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/zendesk/sources/ticket-solved/ticket-solved.mjs

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `categoryId` | `string` | No | The ID of the trigger category. See the docs here Options are loaded from the connected account. |
| `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 |
| `fields` | `string[]` | No | Ticket fields to be included in the incoming webhook payload Options are loaded from the connected account. |
| `jsonBody` | `string` | No | Custom JSON Body of the incoming payload. Setting jsonBody will overwrite the fields prop |

## Returns

Events emitted by Zendesk.

## Run it

**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 deployed = await pd.triggers.deploy({
  id: "zendesk-ticket-solved",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    zendesk: { authProvisionId: "apn_xxxxxxx" },
    categoryId: "Trigger Category ID",
    customSubdomain: "Custom Subdomain",
  },
  webhookUrl: "https://example.com/webhooks/zendesk",
})

console.log(deployed.id)
```

**cURL**

```bash
curl -X POST https://api.pipedream.com/v1/connect/{project_id}/triggers/deploy \
  -H "Content-Type: application/json" \
  -H "X-PD-Environment: production" \
  -H "Authorization: Bearer {access_token}" \
  -d '{
    "external_user_id": "{external_user_id}",
    "id": "zendesk-ticket-solved",
    "webhook_url": "https://example.com/webhooks/zendesk",
    "configured_props": {
      "zendesk": { "authProvisionId": "apn_xxxxxxx" },
      "categoryId": "Trigger Category ID",
      "customSubdomain": "Custom Subdomain"
    }
  }'
```

**MCP**

MCP servers expose Zendesk actions as on-demand tools.

Ticket Solved (Instant) is an event source, so your application deploys it with the Connect SDK or API and then either receives each event at a webhook URL or retrieves events on demand with the trigger events API.

## Event delivery

Every event is sent to the HTTP endpoint you choose when you deploy the source. Or: no webhook required — your app or agent can fetch recent events from the [trigger events API](https://pipedream.com/docs/connect/api-reference/list-trigger-events.md) instead.

---

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