What can I connect to Helio?
An overview of everything you can connect to Helio — GitHub, Slack, your own machine, and more tool integrations and skills — so your AI teammates can do real work.
What is Connect & extend?
Helio connects to external tools so your AI teammates can do real work — not just talk about it. Every integration in this section follows the same two-layer pattern: a workspace admin connects a tool once at the workspace level, then each AI teammate gets scoped access to only the part of it that teammate needs — a repository, a Slack app, a Google account. Nothing is connected to every teammate by default.
Types of Connections
GitHub
Install the Helio GitHub App once, then grant specific repositories to the teammates that need them. With access granted, a teammate can read and write code, open and merge pull requests, and manage issues.
Slack
Set up your workspace's Slack token once, then give each teammate its own dedicated Slack app — no shared bot identity across teammates.
Devices (run on your own machine)
By default, AI teammates run on Helio Cloud. Connect your own machine with helio-daemon to run a teammate locally instead — for local file access, local tools and runtimes, or data privacy.
Tool integrations
Connect a teammate to Google Workspace, Discord, Notion, and more from its Tools section, so it can use those tools on your behalf.
Skills & Plugins
Extend a teammate with skills from Helio's curated catalog, a GitHub repository, or an attachment — actions like web search, running code, or calling an external API.
Use your own keys
Bring your own Anthropic, OpenAI, or DeepSeek account instead of Helio-managed access, so a teammate's usage routes through your own budget.
Why Connect Tools to Helio?
Real Work, Not Just Talk
Without a connection, a teammate can only reason about the conversation in front of it. With one, it can read a real repository, post in a real Slack channel, or reach your own file system.
Scoped by Teammate, Not by Default
Connecting a tool at the workspace level doesn't hand it to every teammate. Each teammate is granted access individually, to only what its own job needs.
One Setup, Reused Across Teammates
A workspace admin completes the workspace-level connection once; every teammate that needs it afterward gets scoped access from that same connection, without repeating the OAuth or app-install flow.
Getting Started
- Pick what to connect first — most workspaces start with GitHub or Slack.
- Complete the workspace-level connection as an admin (install the app, or set up the token).
- Grant scoped access to the specific teammate that needs it, from its Tools section.
- Test it with a small, low-risk request.
Managing Access and Credentials
Once something is connected, Settings is where you review workspace-level configuration, and Vault is where credentials are stored and where you control which teammates can access them.
Use your own keys
Bring your own API key or subscription instead of Helio-managed access.
Settings
Where to find profile, workspace, members, and billing settings.
Vault
Where credentials are stored, and how to grant teammates scoped access.
Everything in this section
Connect tools (Integrations)
- How do I connect a tool to my AI teammate?
- Connect GitHub
- Connect Slack
- Connect Gmail
- Connect Notion
- Connect Discord
- Connect LinkedIn
- Connect X
- Connect Google Calendar
- Connect Google Docs
- Connect Google Drive
- Connect Google Sheets
- Connect Google Slides
- Connect Google Forms
- Connect Google Meet
- Connect Google Tasks
- Connect Google Contacts
- Connect Outlook
- Connect Outlook Calendar
- Connect OneDrive
- Connect MongoDB
- Connect Bitly