# Integrations

Volobox is one workspace, but it does not ask you to leave the tools your company already depends on. Administrators connect or turn on each service once, and people then work with their repositories, calendars and files from inside Volobox. Administrators see the state of every connection in one place, marked ready, needing attention, not set up, or turned off on purpose.

![Organization Settings, Integrations tab: the status list of what the organization is connected to, with GitHub, GitLab, Azure DevOps, Models, Execution hosts, OneDrive and SharePoint and Push notifications each marked Ready, above the Microsoft 365 connection.](https://volobox.io/docs/images/integrations-overview.light.webp)

*The Integrations tab of Organization Settings: GitHub, GitLab, Azure DevOps, Models, Execution hosts and OneDrive and SharePoint, each with its status and when it was last checked.*

## Code hosts

- **GitHub**: Volobox connects through a GitHub App that belongs to your own organization, so it sees only the organizations you install it on. Repositories, pull requests, branches, and issues mirrored as tasks or requests. See [Connect GitHub](/docs/connect-github).
- **GitLab.com**: each GitLab group connects with a service account, and each person can link their own GitLab identity for pushes. Repositories, merge requests, coding sessions and issue mirroring. See [Connect GitLab](/docs/connect-gitlab).
- **Azure Repos**: repositories from Azure DevOps projects you enable, with coding sessions, branch previews and pull requests. See [Connect Azure DevOps](/docs/connect-azure-devops).

What a project does with its repositories is on [Coding](/docs/coding).

## Azure DevOps

Projects link Azure DevOps pipelines and start runs from Volobox, and one page shows those runs across projects. Azure DevOps work items can be synchronized with a project. See [Connect Azure DevOps](/docs/connect-azure-devops) and [Coding](/docs/coding).

## Microsoft 365

On Volobox Cloud, one **Microsoft 365** connection serves several features without an app registration of your own.

> **Note:** Self-hosted deployments use their own Microsoft Entra app registration instead.

- **Microsoft Entra ID sign-in** for your organization's members. See [Set up Microsoft Entra ID sign-in](/docs/entra-id-sign-in).
- **Outlook calendar** sync: events appear in your agenda and can block meetings, while teammates see only that you are busy. See [Meetings](/docs/meetings).
- **Microsoft Teams** meetings created from Volobox. See [Meetings](/docs/meetings).
- **OneDrive and SharePoint** in Files, read only: Volobox previews and searches the files but never stores their contents and never changes anything there. See [Docs and files](/docs/docs-and-files).

## Google

- **Google Calendar** sync, including answering invitations and copying Volobox meetings to Google. Other calendars can be added by their iCal address. See [Meetings](/docs/meetings).
- **Google Meet** as a meeting provider. See [Meetings](/docs/meetings).
- **Google Drive** in Files, read only, for each person's own Drive and for shared drives an administrator connects for the organization. See [Docs and files](/docs/docs-and-files).
- **Google Workspace mailbox** for Mail: a team answers a shared address such as sales@ through an account an administrator connects. Volobox reads that address's mail and sends the team's replies, and changes nothing else in Gmail. See [Mail](/docs/mail).

## Video meetings

A meeting planned in Volobox can be held on **Volobox Call**, **Zoom**, **Microsoft Teams**, **Google Meet**, **Jitsi** or a custom link.

A Volobox agent can also join a Google Meet, Zoom or Microsoft Teams call, to answer by voice or only to take notes.

> **Note:** In Meet and Teams someone admits the agent. In Zoom it joins through the sender's own Zoom connection.

See [Meetings](/docs/meetings) and [Chat and calls](/docs/chat-and-calls).

## Models

Volobox works with the models included in your workspace, and with model providers you add with your own keys where your plan includes them (see [Pricing](/pricing)). See [Add a model provider](/docs/add-model-provider) and [Deployment and models](/docs/deployment-and-models).

## MCP

MCP works in both directions. External agents call Volobox's hosted MCP server, and your agents call the external MCP servers your administrators connect, with the tools and the people who may use each server chosen per server.

See [Connect an MCP client](/docs/connect-mcp-client) and [API, MCP and webhooks](/docs/api-and-mcp).

## API and webhooks

The public HTTP API lets scripts and company tools read and change workspace work with the access they are given. Signed webhooks tell another system when a task closes, a pull request merges or a customer replies, without polling.

See [Make your first API call](/docs/first-api-call), [Receive and verify webhooks](/docs/receive-webhooks) and [API, MCP and webhooks](/docs/api-and-mcp).

## Related

- [Coding](/docs/coding)
- [Meetings](/docs/meetings)
- [Docs and files](/docs/docs-and-files)
- [API, MCP and webhooks](/docs/api-and-mcp)
- [Platform](/product/platform)
