Vercel Connect

EVE supports plugging in open-source adapters such as Postgres, OpenAI Responses API, and Docker, and can also be deployed to Vercel in one click using Vercel Workflows, Sandbox, and Vercel Connect.

Vercel Connect triggers can be toggled on or off at any time in the connector settings without rebuilding the connection.

Vercel Connect previously supported Webhook triggers for Slack, Discord, Microsoft Teams, GitHub and Linear.

Vercel Connect verifies incoming Webhook requests on the developer's behalf and handles heartbeats and verification challenges on the provider side.

The Resend and Telegram Webhooks are registered automatically by Vercel Connect, so developers do not need to go to the provider's dashboard to configure them manually.

Twilio, Notion and X require manual webhook setup on the provider side, including obtaining the webhook URL from Connect and pasting it into the provider's configuration.

Vercel Connect provides a Live view in the connector's Observability tab, allowing real-time observation of incoming trigger events and request details.

A category slug is a unique string identifier that Vercel Connect defines for its service classification system, usually a short lowercase English word (such as `ai`, `data`, `crm`), designed specifically for command-line arguments and API calls.

This feature is currently available in the Stripe connector.

Vercel Connect currently supports three Stripe connection methods: Managed API Key, MCP, and Bring-your-own API key.

This update did not change the existing MCP and bring-your-own-key integration paths, and existing projects require no migration.

Vercel Functions receive the platform-issued token in the request headers, which the SDK reads directly without an extra fetch; the platform reuses unexpired tokens, while Vercel Connect caches vendor tokens in-process and refreshes them as they near expiry.

Vercel Connect lets apps and agents request vendor tokens at runtime using their deployment identity, without storing long-lived keys in environment variables.

Configuring Secure Compute routing does not require writing additional network configuration code.

This update only changes the network path of requests, and the credential management mechanism remains unchanged, so developers still do not need to store long-lived provider keys or build their own OAuth flow.

Requests to obtain and refresh access tokens also go through Secure Compute routing, consistent with business API calls.

The Secure Compute routing setting only applies to provider requests sent by Connect and does not affect the application's own direct API routing.

The request when first creating a connector and all provider discovery requests bypass the selected network and connect directly to the provider, not going through the static IP.

When the selected network is unavailable, routed requests fail directly rather than falling back to Connect's shared IP, which is an intentional design choice.

Vercel Connect previously used a shared IP pool for outbound requests, which could not meet the requirements of enterprise-grade service providers that need IP allowlists.