Deploy projects and manage environment variables on Vercel.
Vercel currently provides 6 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
List Projects
Retrieve all Vercel projects for the authenticated user or team.
Create Deployment
Create a deployment for an existing Vercel project using either a redeploy source deployment ID or a git source payload.
Get Deployment Status
Retrieve a deployment and inspect its current status.
List Environment Variables
Retrieve environment variables for a Vercel project.
Upsert Environment Variable
Create or update a Vercel environment variable using Vercel's upsert API.
Custom API Call
Make a custom API call to Vercel. The Authorization header is injected automatically. If your connection uses Team ID or Team Slug, add `teamId` or `slug` manually in the URL or Query Parameters for team-scoped requests.
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Use a change in Coherence to run a supported Vercel action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
List Projects
Combine Vercel with another integration and Coherence records to connect product and engineering activity to the customers and work it affects.
Starts with
A Coherence workflow starts
Finishes with
List Projects, then preserve the outcome in Coherence
The exact authentication fields depend on Vercel. The workflow structure stays straightforward:
Authorize the Vercel account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Vercel or provide a complementary trigger or action.
Vercel currently provides 6 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
Vercel currently lists 0 triggers and 6 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Vercel triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
