Connect Google Drive, Slack and GitHub
Step by step for three of the most used tools: how each one signs in, what to grant, and how to use it on the Canvas.
Updated September 30, 2026 · 1 min read
Before you start
- Open Connections: each tool has its own dialog with these steps.
- OAuth (“Sign in with…”) appears only where this server has it configured; otherwise use a token.
- Grant the least your agents need: read-only is enough to start.
Google Drive
Sign in with Google
In Connections, open Google Drive and sign in to grant read access.
Test
The connection is tested right away; Connected means agents can read Drive through Google's MCP server.
Slack
Sign in, or create an app
Sign in with Slack, or create a Slack app and install it in your workspace.
Copy the bot token
From the app's OAuth & Permissions page, copy the Bot User OAuth Token (
xoxb-…) and paste it into the dialog.Invite the bot
Add the app to the channels your agents post to.
GitHub
Sign in, or create a token
Sign in with GitHub, or create a fine-grained personal access token.
Choose the repositories
Give it access only to the repositories your agents need, read-only to start.
Paste and test
Save it in the dialog; the test checks it against GitHub and its MCP server.
Use it on the Canvas
Add the Connector
From the Connector Hub (Assets panel), pick the tool: the Connector arrives linked under the selected Sub-Agent or Skill.
Link the Skill
Link the Skill that should use the tool to the Connector; optionally set its MCP tool name.
Run
Connectors without a credential of their own use the organization's connection, unless its last test failed.