Connected to the tools you already pay for

Integrations

44 built in · any MCP server

Assistants and automations act inside your existing systems: read the thread, file the document, book the slot, update the ticket. Forty-four connectors ship built in — and because Bee Flow is a Model Context Protocol client, anything with an MCP server connects too. Nothing has to be migrated first.

What connects today

Every item below is a shipped integration with real tools behind it, gated per user, per organisation and per group.

Google Workspace

Gmail

Calendar

Drive

Docs

Sheets

Slides

Contacts

Groups

Keep

Maps

Meet recordings

Microsoft 365

Outlook

Calendar

Contacts

OneDrive

Entra ID SSO & group sync

Nextcloud

Files

Mail

Calendar

Contacts

Deck

Talk

Notes

Tasks

Activity & Notifications

Service management

Jira

ServiceNow

Zendesk

Freshservice

TopDesk

Development

GitHub

YouTrack

n8n

Playwright test runs

Business & back office

AFAS Profit (read-only)

NMBRS payroll (read-only)

SignRequest

Stripe billing

Gamma

LinkedIn posting

Search, voice & media

Web search

Browse a page for real

Speech to text

ElevenLabs voice

Image & video generation

Fireflies transcripts

Dutch legal sources

Rechtspraak.nl

EUR-Lex

Kamerstukken

Officiële Bekendmakingen

Tuchtrecht

The other several thousand

Model Context Protocol

The list above is what we maintain. It is not the limit. Bee Flow is a Model Context Protocol client over stdio and Streamable HTTP, which means any MCP server — the official registry, a vendor's own, or one your team wrote this afternoon — installs and becomes an ordinary integration. Its tools appear alongside the built-in ones, obey the same per-group permissions, and pass through the same redaction layer. Browse the registry from inside the admin, start from a curated catalogue of 89 servers (GitHub, Slack, Notion, Linear, Postgres, Figma), or have an assistant build you a custom REST or remote-MCP connector behind the same SSRF guard as everything else.

Control

Connected is not the same as unrestricted

A person connects their own account

OAuth, on their own credentials

Nothing is connected org-wide by default. An integration acts as the person who authorised it, so an assistant can never read a mailbox its user could not open themselves.

Three gates have to agree

user enabled it, org allows it, group has not switched it off

A tool appears only when all three say yes. Group-level rules use enable-wins semantics, so a deliberate grant is never silently overridden by a broader default.

What comes back is scanned too

Data returned by a tool passes the same redaction layer as anything you type, and the endpoint it came from is resolved to a country at log time - so a transfer outside the EEA is visible rather than assumed.

Missing something you need?

If it has an API or an MCP server, it can be connected — by you, without waiting for us. If you would rather we did it, say what you are trying to reach.