# New Deployment (Instant) — Vercel

> Emit new event when a deployment is created See the documentation.

- Key: `vercel_token_auth-new-deployment-instant`
- Type: Trigger (Instant)
- Version: 0.0.1
- App: Vercel (`vercel_token_auth`) — https://pipedream.com/apps/vercel-token-auth.md
- This page (HTML): https://pipedream.com/apps/vercel-token-auth/triggers/new-deployment-instant
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/vercel_token_auth/sources/new-deployment-instant/new-deployment-instant.mjs

## Description

Emit new event when a deployment is created [See the documentation](https://vercel.com/docs/rest-api/reference/endpoints/webhooks/creates-a-webhook).

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `teamId` | `string` | No | The Team identifier to perform the request on behalf of. Eg. team_1a2b3c4d5e6f7g8h9i0j1k2l Options are loaded from the connected account. |
| `slug` | `string` | No | The Team slug to perform the request on behalf of. Eg. my-team-url-slug Options are loaded from the connected account. |
| `projectIds` | `string[]` | No | The Project identifiers to perform the request on behalf of Options are loaded from the connected account. |

## Returns

Events emitted by Vercel.

## 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: "vercel_token_auth-new-deployment-instant",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    vercel_token_auth: { authProvisionId: "apn_xxxxxxx" },
    teamId: "Team ID",
    slug: "Slug",
  },
  webhookUrl: "https://example.com/webhooks/vercel-token-auth",
})

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": "vercel_token_auth-new-deployment-instant",
    "webhook_url": "https://example.com/webhooks/vercel-token-auth",
    "configured_props": {
      "vercel_token_auth": { "authProvisionId": "apn_xxxxxxx" },
      "teamId": "Team ID",
      "slug": "Slug"
    }
  }'
```

**MCP**

MCP servers expose Vercel actions as on-demand tools.

New Deployment (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/vercel-token-auth.md · All apps: https://pipedream.com/apps