Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Vercel

Deploy projects and manage environment variables on Vercel.

CategoryDeveloper Tools
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Vercel with Flows360

Deploy projects and manage environment variables on Vercel.

Use the Vercel connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and no declared triggers.

Available actions

  • List Projects
  • Create Deployment
  • Get Deployment Status
  • List Environment Variables
  • Upsert Environment Variable
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Vercel
  • Package: @activepieces/piece-vercel@0.1.0
  • Exact artifact digest: sha256:6df52db0d9e3a778984a7faf3eb9167fa844073b4414f762258a37b667a4c774
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • List Projects (list_projects), Retrieve all Vercel projects for the authenticated user or team. Classification: read.
  • Create Deployment (create_deployment), Create a deployment for an existing Vercel project using either a redeploy source deployment ID or a git source payload. Classification: read.
  • Get Deployment Status (get_deployment_status), Retrieve a deployment and inspect its current status. Classification: read.
  • List Environment Variables (list_environment_variables), Retrieve environment variables for a Vercel project. Classification: read.
  • Upsert Environment Variable (upsert_environment_variable), Create or update a Vercel environment variable using Vercel's upsert API. Classification: read.
  • Custom API Call (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. Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects6
Supported actions6
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Vercel Access Token Required · protected credential
  • Team ID Optional
  • Team Slug Optional

Supported objects

ObjectReadWriteNotes
List Projects Yes No Retrieve all Vercel projects for the authenticated user or team.
Create Deployment Yes No Create a deployment for an existing Vercel project using either a redeploy source deployment ID or a git source payload.
Get Deployment Status Yes No Retrieve a deployment and inspect its current status.
List Environment Variables Yes No Retrieve environment variables for a Vercel project.
Upsert Environment Variable Yes No Create or update a Vercel environment variable using Vercel's upsert API.
Custom API Call Yes No 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.

Supported actions

List Projects · Read

Retrieve all Vercel projects for the authenticated user or team.

list_projects · Risk: low · Retry: safe

Inputs

  • search · string · Optional, Filter projects by name.
Create Deployment · Read

Create a deployment for an existing Vercel project using either a redeploy source deployment ID or a git source payload.

create_deployment · Risk: low · Retry: safe

Inputs

  • project · string · Required, Select a Vercel project.
  • deployment_source · string · Required, Choose whether to redeploy a previous deployment or deploy from a connected Git source.
  • source_fields · object · Optional
  • force_new · boolean · Optional, Create a new deployment even if a previous similar deployment exists.
  • skip_auto_detection_confirmation · boolean · Optional, Automatically confirm framework detection without prompting.
Get Deployment Status · Read

Retrieve a deployment and inspect its current status.

get_deployment_status · Risk: low · Retry: safe

Inputs

  • project · string · Required, Select a Vercel project.
  • deployment · string · Required, Select the deployment to inspect.
  • with_git_repo_info · boolean · Optional, Adds gitRepo information when available.
List Environment Variables · Read

Retrieve environment variables for a Vercel project.

list_environment_variables · Risk: low · Retry: safe

Inputs

  • project · string · Required, Select a Vercel project.
  • decrypt · boolean · Optional, Deprecated by Vercel. If enabled, Vercel will attempt to return decrypted values when allowed.
  • git_branch · string · Optional, Optional branch filter. Only valid for preview-scoped variables.
Upsert Environment Variable · Read

Create or update a Vercel environment variable using Vercel's upsert API.

upsert_environment_variable · Risk: low · Retry: safe

Inputs

  • project · string · Required, Select a Vercel project.
  • key · string · Required, Environment variable key.
  • value · string · Required, Environment variable value.
  • type · string · Required, Vercel environment variable type.
  • target · array · Required, Environment(s) where this variable should apply.
  • git_branch · string · Optional, Optional branch. Only valid when Preview is one of the selected targets.
  • comment · string · Optional, Optional note describing the variable usage.
Custom API Call · Read

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.

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Optional query parameters. For team-scoped requests, manually include `teamId` or `slug` here when needed.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Setup

Setup

  1. Add the Vercel connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Vercel Access Token (token), required; stored as a sensitive connection value.
  • Team ID (teamId), optional.
  • Team Slug (slug), optional.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-vercel@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Vercel connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-vercel@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com