CONNECT APP
Build with Vercel
Infrastructure & Cloud
- API key
MCP
Give your agent Vercel tools
Every Vercel action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Vercel account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "vercel_token_auth",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Cancel Deployment:
const result = await mcp.callTool({
name: "vercel_token_auth-cancel-deployment",
arguments: {
team: "Team",
deployment: "Deployment",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "vercel_token_auth",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Cancel Deployment:
result = await session.call_tool("vercel_token_auth-cancel-deployment", {
"team": "Team",
"deployment": "Deployment",
})API PROXY
Call the Vercel API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Vercel API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.vercel.com/v2/user",
})
// Any allowed Vercel endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.vercel.com/v2/user
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkudmVyY2VsLmNvbS92Mi91c2Vy?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Vercel actions from your backend
Connect a user's Vercel account once, then run Cancel Deployment on their behalf from your own code — TypeScript, Python, or plain HTTP.
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 result = await pd.actions.run({
id: "vercel_token_auth-cancel-deployment",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
vercel_token_auth: { authProvisionId: "apn_xxxxxxx" },
team: "Team",
deployment: "Deployment",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="vercel_token_auth-cancel-deployment",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"vercel_token_auth": {"authProvisionId": "apn_xxxxxxx"},
"team": "Team",
"deployment": "Deployment",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-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-cancel-deployment",
"configured_props": {
"vercel_token_auth": { "authProvisionId": "apn_xxxxxxx" },
"team": "Team",
"deployment": "Deployment"
}
}'TOOLS
Vercel actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Cancel Deployment
actionCancel a deployment which is currently building. See the documentationWritev0.0.6 -
Create Deployment
actionCreate a new deployment from a GitHub repository. See the documentationWritev0.0.6 -
List Deployments
actionList deployments under the account corresponding to the API token. See the documentationRead-onlyv0.0.6
-
Deployment Canceled (Instant)
triggerEmit new event when a deployment is canceled See the documentation.Instantv0.0.1 -
Deployment Error (Instant)
triggerEmit new event when a deployment encounters an error See the documentation.Instantv0.0.1 -
Deployment Succeeded (Instant)
triggerEmit new event when a deployment successfully completes See the documentation.Instantv0.0.1 -
New Deployment
triggerEmit new event when a deployment is createdv0.0.5 -
New Deployment (Instant)
triggerEmit new event when a deployment is created See the documentation.Instantv0.0.1
MULTI-APP
Use Vercel with other popular apps
Most products don't stop at one integration. Pair Vercel with the other apps your users rely on, and ship use cases that span both.
- App slug
- vercel_token_auth
- Authentication
- API key
- Categories
- Infrastructure & Cloud
- Actions
- 3
- Triggers
- 5
- API proxy
- Available