Documentation Index

Fetch the complete documentation index at: https://veryfront.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

​

Integrations

​

Prerequisites

• A Veryfront project with a configured agent (see Agents).
• Provider credentials for each integration you enable: either a Veryfront Cloud token plus a project reference, or per-user OAuth credentials (see OAuth).
• veryfront.config.ts is editable in your repo.

​

How it works

• The runtime reads integration config locally, syncs it to the API when needed, and fetches remote tool definitions per request
• The API / service layer is responsible for OAuth, token storage, and remote integration execution
• Config-driven: adding github: {} to the integrations record enables all GitHub tools instantly
• Per-user tokens: set perUser: true so each end-user authenticates with their own account
• Tool allowlisting: use tools: ["send-message"] to expose only specific tools

​

Configuration

// veryfront.config.ts
import { defineConfig } from "veryfront";

export default defineConfig({
  integrations: {
    // All tools, project-level token
    github: {},

    // Only specific tools
    slack: {
      tools: ["send-message", "list-channels"],
    },

    // Per-user tokens (each end-user authenticates individually)
    linear: {
      perUser: true,
    },

    // API-key based (no OAuth needed)
    stripe: {},
  },
});

​

Authentication flow

1. Tool returns { error: "authentication_required", connectUrl: "..." }
2. Agent surfaces the connect URL to the user
3. User selects the connect URL and completes the configured OAuth app, provider consent screen, and callback flow
4. The backing API layer stores the resulting token according to its configured token store
5. Subsequent tool calls can use that token automatically
6. Refresh behavior depends on the provider and the API/service layer you run behind these endpoints

​

OAuth credentials and deployment model

​

BYO Credentials

GITHUB_CLIENT_ID=<GITHUB_CLIENT_ID>
GITHUB_CLIENT_SECRET=<GITHUB_CLIENT_SECRET>

​

API setup for OAuth credentials

​

Provider registration

https://<api-host>/api/oauth/callback/{integration-name}

{PREFIX}CLIENT_ID=...
{PREFIX}CLIENT_SECRET=...

GITHUB_CLIENT_ID=<GITHUB_CLIENT_ID>
GITHUB_CLIENT_SECRET=<GITHUB_CLIENT_SECRET>
GOOGLE_CLIENT_ID=<GOOGLE_CLIENT_ID>
GOOGLE_CLIENT_SECRET=<GOOGLE_CLIENT_SECRET>
SLACK_CLIENT_ID=<SLACK_CLIENT_ID>
SLACK_CLIENT_SECRET=<SLACK_CLIENT_SECRET>

​

Google APIs (shared credentials)

• Google Calendar API
• Gmail API
• Google Docs API
• Google Drive API
• Google Sheets API

​

Microsoft APIs (shared credentials)

​

API-Key Integrations (no OAuth setup needed)

​

Available integrations

​

Project management

​

Code & DevOps

​

Communication

​

Documents & Storage

​

CRM & Sales

​

Databases

​

Design

​

Analytics

​

Finance & Accounting

​

Support

​

Calendar & Meetings

​

Marketing

​

E-Commerce

​

Social

​

Verify it worked

1. Restart veryfront dev. The dev log lists the integration tools that were registered.
2. From an agent that includes the integration tools, send a message that exercises one tool. The AG-UI stream should include a tool call event with the integration’s tool id and a non-error result.
3. For per-user OAuth integrations, confirm the user has authorised the provider first (see OAuth). Calls fail with 401 if the user has no token.

​

Next

• Sandbox: run isolated commands and file operations
• CLI-first knowledge ingestion: ingest documents into project knowledge

​

Related

• Agents: agents use integration tools
• Tools: define custom tools
• OAuth: configure OAuth-backed providers
• veryfront/integrations: integration metadata reference
• Configuration: configure project settings