# Status Changed — FTrack

> Triggered when the status of an item is changed. See the documentation

- Key: `ftrack-status-changed`
- Type: Trigger (Polling)
- Version: 0.0.1
- App: FTrack (`ftrack`) — https://pipedream.com/apps/ftrack.md
- This page (HTML): https://pipedream.com/apps/ftrack/triggers/status-changed
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/ftrack/sources/status-changed/status-changed.mjs

## Description

Triggered when the status of an item is changed. [See the documentation](https://help.ftrack.com/en/articles/1040498-operations#query)

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `timer` | `$.interface.timer` | Yes | How often to poll the API |

## Returns

Events emitted by FTrack.

## 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: "ftrack-status-changed",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    ftrack: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
  },
  webhookUrl: "https://example.com/webhooks/ftrack",
})

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": "ftrack-status-changed",
    "webhook_url": "https://example.com/webhooks/ftrack",
    "configured_props": {
      "ftrack": { "authProvisionId": "apn_xxxxxxx" },
      "timer": { "intervalSeconds": 900 }
    }
  }'
```

**MCP**

MCP servers expose FTrack actions as on-demand tools.

Status Changed 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/ftrack.md · All apps: https://pipedream.com/apps