Build and extend
Integrations
What Volobox connects to, by area: code hosts, Azure DevOps, Microsoft 365, Google, video meetings, models, MCP, the API and webhooks.
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.
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.
- 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.
- Azure Repos: repositories from Azure DevOps projects you enable, with coding sessions, branch previews and pull requests. See Connect Azure DevOps.
What a project does with its repositories is on 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 and 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.
- Outlook calendar sync: events appear in your agenda and can block meetings, while teammates see only that you are busy. See Meetings.
- Microsoft Teams meetings created from Volobox. See 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.
- Google Calendar sync, including answering invitations and copying Volobox meetings to Google. Other calendars can be added by their iCal address. See Meetings.
- Google Meet as a meeting provider. See 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.
- 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.
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 and 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). See Add a model provider and 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 and API, MCP and webhooks.
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, Receive and verify webhooks and API, MCP and webhooks.