Vercel TRIGGER
Deployment Succeeded (Instant)
- Trigger
- Instant
- API key
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Vercel account, configure the source, and choose the webhook where your backend receives events.
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-deployment-succeeded-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 -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-deployment-succeeded-instant",
"webhook_url": "https://example.com/webhooks/vercel-token-auth",
"configured_props": {
"vercel_token_auth": { "authProvisionId": "apn_xxxxxxx" },
"teamId": "Team ID",
"slug": "Slug"
}
}'MCP servers expose Vercel actions as on-demand tools.
Deployment Succeeded (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.MCP exposes on-demand actions. Event sources are deployed through the Connect SDK or API because they continue listening after the initial request.
SCHEMA
Configuration
These inputs define which events the source watches. Dynamic options are loaded from the connected account.
| Property | Type | Description |
|---|---|---|
teamId Team ID | string | The Team identifier to perform the request on behalf of. Eg. team_1a2b3c4d5e6f7g8h9i0j1k2l Optional Dynamic |
slug Slug | string | The Team slug to perform the request on behalf of. Eg. my-team-url-slug Optional Dynamic |
projectIds Project IDs | string[] | The Project identifiers to perform the request on behalf of Optional Dynamic |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Vercel through Pipedream managed auth.
02
Deploy
Your backend deploys this source with that user's own configuration.
03
Webhook delivery
Every event is sent to the HTTP endpoint you choose when you deploy the source — as it happens.
OR
On-demand retrieval
No webhook required. Your app or agent can fetch recent events from the trigger events API.
REFERENCE
Trigger details
- Registry key
- vercel_token_auth-deployment-succeeded-instant
- Version
- 0.0.1
- App
- Vercel
- Authentication
- API key
- Delivery
- Instant event
- Output
- Events emitted by Vercel.
- Source
- View on GitHub ↗