Overskill Overskill
Log in Sign up & build
Developer docs

Vercel integration

Create an internal deployment-status view using a known Vercel deployment ID or URL. Display the state and project context before offering any separate deployment action.

Catalog updated November 2026 146 catalog actions

Back to Vercel overview
Provider
vercel
Category
Other
Setup
User-supplied API key
Actions
146 listed in catalog

Start with one action

  1. Define the result. Choose one task, the data it needs, and who may run it. Start with a read when possible.
  2. Check access. Review the setup state below and the connection available to your workspace or app user. A catalog listing does not confirm that an account is connected.
  3. Inspect the current inputs. Ask the editor to discover the actions for Vercel and inspect the selected action's required inputs and returned data before implementing it.
  4. Verify with test data. Compare the result with what you expected. Check unauthorized access and error handling before relying on the feature.
Developer details: the supplied app client

Generated apps that include src/lib/composio.ts expose the following import in their React app code:

import { executeAction } from "@/lib/composio";

Its call signature is executeAction(actionName, params, options?). Supply the exact current action name and inputs from its specification. This import identifies the helper; it is not a complete or tested integration example.

The editor's os-list-integrations tool discovers an integration using integration_slug. Include both integration_slug and action_slug to retrieve the selected action's input and output schemas. Do not invent parameters from a catalog description.

executeAction requires a signed-in app user and any connection the action needs. The separate publicAction helper is only for a confirmed no-auth toolkit on an enabled public proxy. It does not make OAuth or API-key integrations anonymous.

Existing apps may contain an older client. Inspect the app's files and connection selection before changing a call. Keep provider credentials out of browser code and test failure handling; this guide does not promise automatic retries or synchronization.

Setup

This setup uses a supplied Vercel API key. Follow the available connection form, then verify one action after setup.

Catalog actions

This saved catalog snapshot lists 146 actions. Names and inputs can change. Inspect the current action specification and connection requirements before adding a call; this list is not an execution test.

Show all 146 actions
  • VERCEL_CREATE_DNS_RECORD
  • VERCEL_CREATE_EDGE_CONFIG
  • VERCEL_CREATE_EDGE_CONFIG_TOKEN
  • VERCEL_CREATE_NEW_DEPLOYMENT
  • VERCEL_CREATE_OR_TRANSFER_DOMAIN
  • VERCEL_CREATE_PROJECT
  • VERCEL_CREATE_PROJECT2
  • VERCEL_CREATE_PROJECT_ENV
  • VERCEL_CREATE_PROJECT_TRANSFER_REQUEST
  • VERCEL_CREATE_SHARED_ENV_VARIABLE
  • VERCEL_CREATE_WEBHOOK
  • VERCEL_DANGEROUSLY_DELETE_BY_SRC_IMAGES
  • VERCEL_DANGEROUSLY_DELETE_BY_TAGS
  • VERCEL_DELETE_ALIAS
  • VERCEL_DELETE_AUTH_TOKEN
  • VERCEL_DELETE_DATA_CACHE_PURGE_ALL
  • VERCEL_DELETE_DEPLOYMENT
  • VERCEL_DELETE_DNS_RECORD
  • VERCEL_DELETE_DOMAIN
  • VERCEL_DELETE_EDGE_CONFIG
  • VERCEL_DELETE_EDGE_CONFIG_TOKENS
  • VERCEL_DELETE_PROJECT
  • VERCEL_DELETE_PROJECT_ENV
  • VERCEL_DELETE_ROLLING_RELEASE_CONFIG
  • VERCEL_DELETE_SHARED_ENV_VARIABLE
  • VERCEL_DELETE_WEBHOOK
  • VERCEL_DOWNLOAD_ARTIFACT
  • VERCEL_EDIT_PROJECT_ENV
  • VERCEL_FILTER_PROJECT_ENVS
  • VERCEL_GET_ACTIVE_ATTACK_STATUS
  • VERCEL_GET_ALIAS
  • VERCEL_GET_ALL_LOG_DRAINS
  • VERCEL_GET_ARTIFACT_INFO
  • VERCEL_GET_AUTH_TOKEN
  • VERCEL_GET_AUTH_USER
  • VERCEL_GET_BULK_AVAILABILITY
  • VERCEL_GET_CACHE_STATUS
  • VERCEL_GET_CERTS
  • VERCEL_GET_CONFIGURATIONS
  • VERCEL_GET_CONTACT_INFO_SCHEMA
  • VERCEL_GET_DEPLOYMENT
  • VERCEL_GET_DEPLOYMENT_DETAILS
  • VERCEL_GET_DEPLOYMENT_EVENTS
  • VERCEL_GET_DEPLOYMENT_EVENTS2
  • VERCEL_GET_DEPLOYMENT_FILE_CONTENTS
  • VERCEL_GET_DEPLOYMENT_LOGS
  • VERCEL_GET_DEPLOYMENT_LOGS2
  • VERCEL_GET_DEPLOYMENTS
  • VERCEL_GET_DOMAIN
  • VERCEL_GET_DOMAIN_CONFIG
  • VERCEL_GET_DOMAIN_TRANSFER_INFO
  • VERCEL_GET_DRAINS
  • VERCEL_GET_EDGE_CONFIG
  • VERCEL_GET_EDGE_CONFIG_BACKUP
  • VERCEL_GET_EDGE_CONFIG_ITEM
  • VERCEL_GET_EDGE_CONFIG_SCHEMA
  • VERCEL_GET_EDGE_CONFIG_TOKEN
  • VERCEL_GET_FIREWALL_CONFIG
  • VERCEL_GET_GIT_NAMESPACES
  • VERCEL_GET_PROJECT
  • VERCEL_GET_PROJECT2
  • VERCEL_GET_PROJECT_DOMAIN
  • VERCEL_GET_PROJECT_DOMAINS
  • VERCEL_GET_PROJECT_ENV
  • VERCEL_GET_PROJECTS
  • VERCEL_GET_PROMOTE_ALIASES
  • VERCEL_GET_ROLLING_RELEASE
  • VERCEL_GET_ROLLING_RELEASE_BILLING_STATUS
  • VERCEL_GET_ROLLING_RELEASE_CONFIG
  • VERCEL_GET_RUNTIME_LOGS
  • VERCEL_GET_SHARED_ENV_VAR
  • VERCEL_GET_SHARED_ENV_VARIABLES
  • VERCEL_GET_TEAM
  • VERCEL_GET_TEAMS
  • VERCEL_GET_TLD_INFO
  • VERCEL_GET_TLD_PRICE
  • VERCEL_GET_USER_EVENTS
  • VERCEL_GET_WEBHOOK
  • VERCEL_INVALIDATE_CACHE_BY_SRC_IMAGES
  • VERCEL_INVALIDATE_CACHE_BY_TAGS
  • VERCEL_LIST_ALIASES
  • VERCEL_LIST_ALL_DEPLOYMENTS
  • VERCEL_LIST_AUTH_TOKENS
  • VERCEL_LIST_DEPLOYMENT_ALIASES
  • VERCEL_LIST_DEPLOYMENT_CHECKS
  • VERCEL_LIST_DEPLOYMENT_FILES
  • VERCEL_LIST_DNS_RECORDS
  • VERCEL_LIST_DOMAINS
  • VERCEL_LIST_EDGE_CONFIG_BACKUPS
  • VERCEL_LIST_EDGE_CONFIG_ITEMS
  • VERCEL_LIST_EDGE_CONFIGS
  • VERCEL_LIST_EDGE_CONFIG_TOKENS
  • VERCEL_LIST_ENV_VARIABLES
  • VERCEL_LIST_FIREWALL_EVENTS
  • VERCEL_LIST_INTEGRATION_LOG_DRAINS
  • VERCEL_LIST_PROJECT_CUSTOM_ENVIRONMENTS
  • VERCEL_LIST_PROJECT_MEMBERS
  • VERCEL_LIST_PROJECTS
  • VERCEL_LIST_SUPPORTED_TLDS
  • VERCEL_LIST_TEAM_MEMBERS
  • VERCEL_LIST_TEAMS
  • VERCEL_LIST_WEBHOOKS
  • VERCEL_MOVE_PROJECT_DOMAIN
  • VERCEL_PAUSE_PROJECT
  • VERCEL_READ_FIREWALL_CONFIG
  • VERCEL_RECORD_EVENTS
  • VERCEL_REMOVE_PROJECT_DOMAIN
  • VERCEL_REPLACE_FIREWALL_CONFIG
  • VERCEL_REQUEST_DELETE_USER
  • VERCEL_REQUEST_PROMOTE
  • VERCEL_SEARCH_REPO
  • VERCEL_TEST_DRAIN
  • VERCEL_TRANSFER_IN_DOMAIN
  • VERCEL_UNLINK_SHARED_ENV_VARIABLE
  • VERCEL_UNPAUSE_PROJECT
  • VERCEL_UPDATE_ATTACK_CHALLENGE_MODE
  • VERCEL_UPDATE_DNS_RECORD
  • VERCEL_UPDATE_DOMAIN
  • VERCEL_UPDATE_EDGE_CONFIG
  • VERCEL_UPDATE_EDGE_CONFIG_ITEMS
  • VERCEL_UPDATE_EDGE_CONFIG_SCHEMA
  • VERCEL_UPDATE_FIREWALL_CONFIG
  • VERCEL_UPDATE_PROJECT
  • VERCEL_UPDATE_PROJECT2
  • VERCEL_UPDATE_PROJECT_DATA_CACHE
  • VERCEL_UPDATE_PROJECT_DOMAIN
  • VERCEL_UPDATE_PROJECT_PROTECTION_BYPASS
  • VERCEL_UPDATE_SHARED_ENV_VARIABLE
  • VERCEL_UPDATE_STATIC_IPS
  • VERCEL_UPDATE_TEAM
  • VERCEL_UPDATE_URL_PROTECTION_BYPASS
  • VERCEL_UPLOAD_ARTIFACT
  • VERCEL_UPLOAD_FILE
  • VERCEL_VERIFY_PROJECT_DOMAIN

Show deployment state without starting another deploy

Illustrative acceptance test, not a recorded customer result. Ask the editor to check the current supported action and inputs before building it. Provider API documentation does not guarantee that every action is exposed by your connection.

Action to inspect

VERCEL_GET_DEPLOYMENT

Listed in the saved Overskill catalog on November 3, 2026. Ask the editor for its current inputs and verify your connection; catalog presence is not a completed execution test.

Sample input

Deployment: one known test deployment ID; display project, URL and ready state

What to verify

The app shows the same deployment and state as the provider. A missing or unauthorized deployment is displayed as unavailable, not successful.

Account and permissions

A Vercel connection allowed to read the deployment and its owning team or project. Confirm team context when projects span multiple accounts.

Limits to plan for

A deployment record is not proof that the production alias points to it. Compare the requested target and current state; do not treat a queued build as live.

Read the provider reference

Editorial review: 2026-11-03

Build with Vercel

Describe one task you want your app to perform with Vercel. Check the connection requirements, then verify the result in your app. Building and running the feature may use credits; review current pricing.

Start building with Vercel View Vercel overview