Developer tools
Connect your agents to Vercel.
Agents read build logs, explain failed deployments, redeploy, and manage environment variables, domains, and feature flags. A workflow can start when a deployment fails or is promoted, a certificate renewal fails, an environment variable changes, or Vercel raises an alert.
5,000 free credits to start.
Agent reach
Vercel REST API
The full surface, searched at run time.
Connect with
- API key
- Your own OAuth app
Use an access token or your own Vercel integration through OAuth. Triggers with a token need a Pro or Enterprise team. With your own integration, you point its webhook at Helios.
Event triggers
Yes · 9 events
Plus manual, schedule, and signed webhook.
What the agent can do
What agents do with Vercel
Helios searches the Vercel REST API at run time. The agent finds the endpoint the task needs and calls it.
- Call Vercel REST API endpoints with your connection's permissions.
- Read deployment build logs to investigate failures.
- List projects and deployments and report their state.
- Redeploy a deployment, promote one to production, or roll back.
- Read, add, and update environment variables for each environment.
- Start a run on deployment, rollback, domain, certificate, environment variable, rolling release, feature flag, alert, and firewall events.
Examples
Tasks you can hand to a Vercel agent
Diagnose failed deployments
When a build fails, the agent reads the logs, investigates the related changes, and opens an issue with the cause.
When a production deployment fails, find the cause and file an issue.
- vercel·read the build logs
- github·compare the commit with the last good one
- github·open an issue with the error and related changes
GitHub issue filed
- `Module not found: @/lib/flags` in the build step
- The import came from the last merged pull request
- Assigned to the pull request's author
Share preview links
When a preview deployment is ready, the agent posts the link and what changed to the team's channel.
When a preview deployment of the web project is ready, post the link to Slack.
- vercel·read the deployment and its branch
- github·summarize the pull request
- slack·post to #web-reviews
Preview shared
- Branch `feature/checkout` is ready to review
- The pull request moves checkout to the new pricing table
Write release notes on promotion
When a deployment reaches production, the agent collects the changes since the last release and posts release notes.
When a deployment is promoted to production, post release notes.
- vercel·find the previous production deployment
- github·list the commits between the two
- slack·post the notes to #releases
Release notes posted
- 6 merged pull requests
- New checkout flow and two bug fixes
Audit environment variables
A scheduled agent compares environment variables across projects and environments and reports gaps.
Every Monday, check that each project has the same keys in Preview and Production.
- vercel·list projects
- vercel·read each project's environment variables
- code·compare keys by environment
- slack·post the gaps to #platform
2 projects with gaps
- `web` is missing `STRIPE_WEBHOOK_SECRET` in Preview
- `docs` has `SEARCH_API_KEY` only in Production
Event triggers
Start a run on Vercel events
Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too.
| Event | What it means |
|---|---|
deployment.failed | A build failed. Filter by project, environment, or branch, then diagnose it. |
deployment.built | A deployment finished building, so an agent can check it or share the preview link. |
deployment.promoted | A deployment was promoted to production. |
deployment.created | A deployment started building. |
deployment.canceled | A deployment was canceled before it finished. |
deployment.rolled_back | Vercel accepted a rollback request, so an agent can open an incident. |
env_variable.updated | An environment variable changed in a project. |
certificate.renewal_failed | A certificate didn't renew, so an agent can check the domain's DNS before it expires. |
alert.triggered | Vercel raised an alert about unusual traffic or errors in a project. |
Works with
Vercel works with the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox.
FAQ
Questions, answered
Put an agent on Vercel.
Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook.