Skip to main content
An integration is a stored set of third-party credentials, such as a bot token or a database connection string, that actions, entry handlers, and MCP tools look up by id. This page lists every integration type, its fields, and what uses it. Values are taken from the running binary; servflowai resource integration describe --all prints the same catalog.

Identity and storage

  • Id. Every integration has an id, such as discord or github-app. Configs reference the integration by this id. The id cannot be changed after the integration is created.
  • Field values. Each field holds either a literal value or a reference to a stored secret. A literal is stored in the integration’s config as typed. A secret reference keeps the value in Secrets, so it never appears in the config.
  • Encryption. When master_key is set under [sqlite], integration config is encrypted at rest. See the Configuration reference.
  • Guided setup. In the dashboard, discord, github_app, and notion_mcp open a guided setup. Every other type opens a form with one input per field. To add one in the dashboard, see Add an integration.

Types

binance

Binance cryptocurrency exchange integration for trading operations.

chromium

Chromium browser automation integration for web scraping and testing.

discord

A Discord bot for one server. It reads that server, and sends messages anywhere it can. To run an agent as a Discord bot, see Connect an agent to Discord.

github_app

A GitHub App’s credentials. The GitHub actions mint installation tokens with them, and the App’s deliveries are signed with its webhook secret.

mongo

MongoDB database integration for document storage and retrieval.

notion_mcp

A Notion workspace connected through Notion’s MCP server. It has no fields. The dashboard connects it through Notion’s OAuth sign-in, and an MCP server tool sends its token.

qdrant

Qdrant vector database for similarity search and vector storage.

sql

SQL database integration supporting PostgreSQL and MySQL.

telegram_bot

A Telegram bot: the token BotFather issued, and the secret its webhook is registered with.

Managing integrations outside the dashboard

CLI

The integration noun of the resource command manages stored integrations. list never includes config. The body names the id, the type, and the config as a JSON string. Each field in the config is an object holding either a value or a secret:

MCP

The management server at /api/mcp exposes list_integrations, get_integration, create_integration, update_integration, delete_integration, list_integration_types, and describe_integration_type.

Connect an agent to Discord

Add a Discord integration and run an agent as a bot.

Entry handlers

The entries that take an integration, and their fields.

Secrets

Store a credential once and reference it from an integration.