Vercel

The Vercel integration enables workflows to monitor deployment events, retrieve production and preview URLs, and trigger actions based on build success or failure. The same credential is also used by the Vercel Sandbox provider for runtime execution.

What you can do

Deployment monitoring: receive build started, succeeded, failed events
Environment access: list deployments and retrieve preview URLs
Build status: check production vs preview deployment health
Webhooks: automatic event ingestion; no manual configuration required
Sandbox execution: (optional) use Vercel Firecracker microVMs as a runtime environment for agents

Connect Vercel

Create a Vercel API token

Go to vercel.com/account/tokens
Click Create
Token name: e.g., "Rensei"
Scope: select your team (or personal account for personal projects)
Expiration: 90 days is recommended; note the expiry date - expired tokens cause integration health failures
Copy the token

Add the token to Rensei

In Rensei, go to Settings → Integrations
Select the Vercel card
Paste your API token
Click Connect

The platform validates the token and automatically subscribes Rensei to deployment events across your Vercel projects. No manual webhook configuration in Vercel is required.

The same token is reused if you enable Vercel Sandbox as an execution provider - see Shared credential for Vercel Sandbox.

Credential summary

Credential field	Value
Vercel API Token	Team- or personal-scoped token
Webhook subscription	Auto-managed on connect
Webhook endpoint	`POST /api/webhooks/ingest/vercel`
Stored	AES-GCM encrypted at workspace level

Webhook setup (automatic)

When you add the Vercel integration, Rensei automatically:

Subscribes to deployment events for all your Vercel projects
Routes events to /api/webhooks/ingest/vercel
Begins receiving real-time deployment notifications

No manual webhook configuration in Vercel is needed.

Deployment events

Rensei receives the following events:

Event	Trigger	Payload
`deployment.created`	Build started	Project, commit, branch, deployment ID
`deployment.succeeded`	Build passed	URL, environment, regions, build duration
`deployment.failed`	Build failed	Error message, logs URL

These events are available as workflow triggers (e.g., trigger.vercel.deployment.succeeded).

Workflow nodes

Vercel integration provides a limited set of workflow nodes (Vercel's REST API is primarily read-only; deployment is managed via Git).

Triggers

Node	Payload
`trigger.vercel.deployment.created`	Project name, branch, commit SHA, deployment ID
`trigger.vercel.deployment.succeeded`	Production/preview URL, build duration, regions
`trigger.vercel.deployment.failed`	Project, error message, build logs URL

Example: Notify on failed production deployment

trigger:
  type: trigger.vercel.deployment.failed
  filter:
    environment: "production"

steps:
  - id: notify
    type: slack.post
    inputs:
      channel: "#deployments"
      message: |
        Vercel build failed for {{ $trigger.vercel.project }}
        Error: {{ $trigger.vercel.error }}
        Logs: {{ $trigger.vercel.logs_url }}

Deployment queries

Node	Description
`vercel.deployment.get`	Fetch deployment details by ID
`vercel.deployment.list`	List recent deployments for a project
`vercel.project.get`	Get project metadata (git link, domain, regions)
`vercel.project.list`	List all projects in your account

Example: Find the latest production deployment

- id: get_latest
  type: vercel.deployment.list
  inputs:
    projectName: "my-app"
    environment: "production"
    limit: 1

- id: verify_url
  type: condition
  condition: "{{ $steps.get_latest.deployments[0].state == 'READY' }}"
  onTrue: [smoke_test]

Shared credential for Vercel Sandbox

If your organization enables Vercel Sandbox as an execution provider, the same Vercel API token is reused for:

Launching microVMs for agent code execution
Managing container lifecycles
Billing and resource tracking

When you configure a Vercel Sandbox pool, you simply select the Vercel integration from Settings → Capacity → Execution Pools. No separate credential is needed.

Refer to Vercel Sandbox for details on runtime execution and region selection.

Limitations

No deployment triggering: Rensei cannot initiate a Vercel build directly (that happens via Git push). Workflows can monitor and respond to builds, but not trigger them.
No environment variables: Rensei cannot read or modify Vercel environment variables via the API.
Read-only projects: Rensei can query project metadata but cannot create or delete projects.

These limitations reflect Vercel's API surface, not Rensei's integration.