# New File Event — Box

> Emit new event when a file is uploaded to, or moved into, the target folder (FILE.UPLOADED), via a Box webhook. Box fires this trigger for both cases, so moving an existing file into the folder also emits an event. See the documentation

- Key: `box-new-file`
- Type: Trigger (Instant)
- Version: 0.1.5
- App: Box (`box`) — https://pipedream.com/apps/box.md
- This page (HTML): https://pipedream.com/apps/box/triggers/new-file
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/box/sources/new-file/new-file.mjs

## Description

Emit new event when a file is uploaded to, or moved into, the target folder (`FILE.UPLOADED`), via a Box webhook. Box fires this trigger for both cases, so moving an existing file into the folder also emits an event. [See the documentation](https://developer.box.com/reference/post-webhooks)

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `webhookTarget` | `string` | Yes | The target item that will be used by webhooks. Options are loaded from the connected account. |
| `includeLink` | `boolean` | No | Upload file to your File Stash and emit temporary download link to the file. See the docs to learn more about working with files in Pipedream. |
| `dir` | `dir` | No | Dir |

## Returns

Events emitted by Box.

## 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: "box-new-file",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    box: { authProvisionId: "apn_xxxxxxx" },
    webhookTarget: "Target",
    includeLink: true,
  },
  webhookUrl: "https://example.com/webhooks/box",
})

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": "box-new-file",
    "webhook_url": "https://example.com/webhooks/box",
    "configured_props": {
      "box": { "authProvisionId": "apn_xxxxxxx" },
      "webhookTarget": "Target",
      "includeLink": true
    }
  }'
```

**MCP**

MCP servers expose Box actions as on-demand tools.

New File Event 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/box.md · All apps: https://pipedream.com/apps