Skip to main content
This page lists every integration type built into ServFlow. The apps ServFlow connects to, such as Slack, Gmail, or Jira, are listed in the integrations directory. Each type’s section says what uses it and lists its fields and its body in a file. servflowai resource integration describe --all prints the same catalog. For what an integration is, see Integrations. To add one in the dashboard, see Add an integration. In a body, each field of config holds either a literal, as {"value": ...}, or the name of a stored secret, as {"secret": "<secret name>"}. Use a secret for every password field. A secret that a body names has to exist before the integration is created. The commands that take a body are in the CLI reference. An integration connected through OAuth, such as Notion, cannot be used until its sign-in finishes. A type with a guided setup opens its own set of screens in the dashboard. Every other type opens a form with one input for each field. OAuth-guided integrations can appear as Not connected until the provider approval finishes; use the row’s Connect integration action to retry the approval.

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.

gitea

A Gitea server and the account the agent acts as on it. Receiving a Gitea webhook needs no integration, because that secret belongs to the webhook and is set on the entry.

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. In the dashboard, the guided setup creates the App and fills in these fields for you.

mongo

MongoDB database integration for document storage and retrieval.

notion_mcp

A Notion workspace connected through Notion’s MCP server. It has no fields in the form. In the dashboard, give it a name and sign in to Notion. An MCP server tool can then use it as its access token. Each notion_mcp integration is one Notion workspace connection. To connect another workspace, create another Notion integration with a different name and complete its sign-in.

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.

Integrations

What an integration is, and the places one is used.

Add an integration

Add one in the dashboard.

Available entry handlers

The entries that take an integration.

Available actions

The actions that take an integration.