Connect an integration

Connect an integration when project work needs an external service or tool.

Steps

Choose the service in the integration catalog.
Connect OAuth when the service needs user or workspace authorization.
For API key, basic auth, and client-credentials integrations, set the environment variables named in the integration’s setup guide (for example STRIPE_SECRET_KEY).
For experimental integrations, set VERYFRONT_EXPERIMENTAL_INTEGRATIONS to all or to a comma-separated list of integration names.
Enable the tools, channels, or storage surfaces the project needs.
Test the integration from the project.
Review access when project ownership changes.

Set credential environment variables

Credential-based integrations (API key, basic auth, client credentials) read their secrets from the project’s environment variables. The integration’s setup guide names the exact keys. Set variables per environment in Studio under the project’s environment settings, or with Create Environment Variable: POST /projects/{project_reference}/environment-variables?environment_id={environment_id}

Terminal

curl -X POST "https://api.veryfront.com/projects/my-project/environment-variables?environment_id=$ENVIRONMENT_ID" \
  -H "Authorization: Bearer $VERYFRONT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "key": "STRIPE_SECRET_KEY", "value": "sk_live_..." }'

For local development, put the same keys in the project’s .env file. See Configuration for how the framework reads them and Projects and configuration for environments.

Try it with REST

List available integrations: GET /integrations

Terminal

curl https://api.veryfront.com/integrations \
  -H "Authorization: Bearer $VERYFRONT_API_KEY"

List connected OAuth accounts: GET /integrations/user-connections

Terminal

curl https://api.veryfront.com/integrations/user-connections \
  -H "Authorization: Bearer $VERYFRONT_API_KEY"

API surfaces

Surface	Start here
REST	Integrations, Project Integrations, OAuth
GraphQL	Integrations, User OAuth Connected Integrations
MCP	List Integrations, List User OAuth Integrations

Verify

Confirm the integration appears in the project. Run a small read-only tool call before using the integration in production work. Tools that change external state are marked as write tools; start with a read. If a credential-based integration fails, confirm the environment variable names match the integration’s setup guide exactly.

Integration surfaces

Surface	Use it for
Integration	Service connected to a project.
OAuth connection	User or workspace authorization.
Tool	Callable action exposed by the service.
Channel	Messaging surface connected to project work.
External storage	Files managed outside Veryfront.

API reference

API	Use
REST	Integrations, integration tools, OAuth, channels, and external storage.
GraphQL	Integration, OAuth, channel, and storage views.
MCP	Integration, OAuth, channel, and storage tools.

Getting Started

Concepts

Conversations API

Guides

Integrations

API Reference

REST API

GraphQL API

MCP API

Connect an integration

Steps

Set credential environment variables

Try it with REST

API surfaces

Verify

Integration surfaces

API reference

​Steps

​Set credential environment variables

​Try it with REST

​API surfaces

​Verify

​Integration surfaces

​API reference

Steps

Set credential environment variables

Try it with REST

API surfaces

Verify

Integration surfaces

API reference