Integrations

Zubo integrates with popular services via pre-built skill packs. Each integration installs one or more skills and requires an API key stored as a secret. You can connect integrations via chat, the dashboard, or the connect_service tool.

Connecting an Integration

There are three ways to connect a service:

1. Chat: Tell Zubo directly — for example, "Connect GitHub with token ghp_abc123". Zubo will store the secret and install the skill pack automatically.
2. Dashboard: Navigate to Settings → Secrets → Add Secret. Enter the secret name and value, then Zubo detects the associated integration and installs the skills.
3. CLI: Run zubo start, then use the connect_service tool programmatically to provide the credentials.

When you connect a service, Zubo performs the following steps:

1. Stores the API key as a secret in the local database
2. Installs the relevant skill pack for that service
3. Makes all integration tools available immediately (hot-loaded — no restart required)

GitHub

Getting a Token

1. Go to github.com/settings/tokens
2. Click “Generate new token (classic)”
3. Select the repo and read:user scopes
4. Copy the generated token

Skills Installed

• github_repos — List and search repositories, view repository details
• github_issues — List, search, and create issues on any accessible repository
• github_prs — List and search pull requests, view PR details and diffs

Example

"Connect GitHub with token ghp_abc123xyz"

After connecting, try: "List my GitHub repos" or "Show open issues on myorg/myrepo"

Google

Getting a Key

1. Go to console.cloud.google.com
2. Create a new project (or select an existing one)
3. Navigate to APIs & Services → Library and enable the Gmail, Calendar, Sheets, Docs, and Drive APIs
4. Go to APIs & Services → Credentials
5. Create an API key or OAuth 2.0 client credentials

Skills Installed

• gmail — Read and list emails, search by query
• google_calendar — List upcoming events, get event details
• google_sheets — Read from and write to spreadsheets
• google_docs — Read document content
• google_drive — List and search files across your Drive

Notion

Getting a Token

1. Go to notion.so/my-integrations
2. Click “New integration”
3. Give it a name and select the workspace
4. Copy the Internal Integration Token
5. Important: Share the databases and pages you want Zubo to access with the integration inside Notion (click “Share” on the page and add the integration)

Skills Installed

• notion_databases — List and search databases in your workspace
• notion_pages — Read and search pages by title or content
• notion_search — Full-text search across the entire connected workspace

Linear

Getting a Key

1. Open Linear and go to Settings → API → Personal API Keys
2. Click “Create key”
3. Copy the generated key

Skills Installed

• linear_issues — List, search, and create issues across your teams
• linear_projects — List projects and their statuses

Jira

Jira requires three secrets: your API token, the email address associated with your Atlassian account, and your Jira domain (e.g., yourcompany.atlassian.net).

Getting a Token

1. Go to id.atlassian.com/manage-profile/security/api-tokens
2. Click “Create API token”
3. Copy the token
4. Store all three secrets:

   "Store my jira_token: atl_abc123..."
   "Store my jira_email: you@company.com"
   "Store my jira_domain: yourcompany.atlassian.net"

Skills Installed

• jira_issues — List and search issues using JQL, view issue details
• jira_boards — List boards and their configurations

Slack (Integration)

The Slack integration allows Zubo to proactively send messages to Slack channels and read channel history. This is used for the agent to interact with Slack on your behalf.

Note: This is different from the Slack channel (configured in Channel Setup), which lets users send messages to Zubo via Slack. The integration allows the agent to proactively interact with Slack channels — sending messages, reading history, and responding to events.

Skills Installed

• slack_messages — Send messages to channels and users, read channel message history

Twitter / X

Getting a Token

1. Go to developer.twitter.com
2. Create a project and app
3. Navigate to Keys and Tokens
4. Generate a Bearer Token

Skills Installed

• twitter_posts — Compose and post tweets

Note: The twitter_posts tool has confirm permission level — the agent will always describe the tweet and ask for your explicit approval before posting. This cannot be bypassed.

Integration Summary

Managing Secrets

All integration secrets are managed through the same unified secret system.

Dashboard

• Navigate to Settings → Secrets & API Keys
• Values are displayed as •••••••• by default
• Click “Reveal” to show the actual secret value
• Click “Edit” to update a secret with a new value
• Click “Delete” to remove a secret entirely (this disables the associated integration)

Chat

You can also manage secrets conversationally:

"List my secrets"
"Delete the github_token secret"
"Update my notion_token to ntn_newvalue123"

Best Practices

• Use minimum required scopes: When creating API tokens, only grant the permissions each service needs. For GitHub, repo and read:user are sufficient — avoid granting admin or delete scopes.
• Rotate API keys periodically: Update your tokens every few months by editing the secret in the dashboard or telling Zubo to update it.
• Check requirements first: Before connecting an integration, review which secrets it needs (see the summary table above) so you can prepare all required credentials.
• Test after connecting: After storing a secret, verify the integration works by asking Zubo to perform a simple action — for example, "List my GitHub repos" or "Show my upcoming calendar events".
• Secrets are excluded from exports: When you run zubo export, secrets and API keys are automatically excluded to prevent accidental credential leakage.
• Store secrets via Zubo: Always use the agent, dashboard, or secret_set tool to store credentials. Never put them in environment variables, configuration files, or skill source code.
• Share Notion pages explicitly: The Notion integration can only access pages and databases that have been explicitly shared with the integration — it does not have access to your entire workspace by default.