Service Connections Catalog

Sophon ships with pre-built connectors for the services teams actually use. Each connector declares its auth method, scopes, endpoints, and credential fields — so configuring it is just clicking through OAuth or pasting an API key, not editing config files.

For the mechanics of adding a connection (OAuth flow, vault storage, multi-account, how a skill receives a credential), see Connections. This page is the catalog.

Google

Gmail

• Auth: OAuth 2.1 + PKCE
• Scopes: gmail.readonly, gmail.modify, gmail.send
• Enables: email.send, email.search, email.reply, email.delete_draft
• Notes: Requires Google Workspace or personal Gmail. Rate-limited server-side by Google.

Google Calendar

• Auth: OAuth 2.1 + PKCE
• Scopes: calendar, calendar.events
• Enables: calendar.list, calendar.create, calendar.update, calendar.delete
• Notes: Multi-calendar support per connection.

Google Drive

• Auth: OAuth 2.1 + PKCE
• Scopes: drive.file, drive.readonly
• Enables: drive.list, drive.upload, drive.download, drive.search

Google Docs / Sheets

• Auth: shared with Drive
• Enables: docs.read, docs.update, sheets.read, sheets.update, sheets.append

Microsoft

Microsoft 365 (Graph API)

• Auth: OAuth 2.1 + PKCE against Azure AD
• Scopes: User.Read, Mail.ReadWrite, Mail.Send, Calendars.ReadWrite, Files.ReadWrite
• Enables: microsoft.mail, microsoft.send_mail, microsoft.calendar, microsoft.onedrive
• Notes: Works with personal Microsoft accounts and Office 365 tenants.

Outlook (standalone)

Configured under Microsoft 365; the microsoft.* tools work against Outlook mail automatically.

OneDrive

• Auth: OAuth 2.1 + PKCE
• Enables: onedrive.list, onedrive.upload, onedrive.download

Teams

• Auth: OAuth 2.1 + PKCE (Bot Framework app)
• Enables: Bot channel adapter — see Teams channel

Developer

GitHub

• Auth: OAuth 2.1 + PKCE (or Personal Access Token for CI-style integrations)
• Scopes: repo, read:user, notifications, workflow
• Enables: github.repos, github.issues, github.create_issue, github.prs, github.search_code
• Notes: Also available via the GitHub MCP server (if you prefer to use MCP instead of the native skill).

GitLab

• Auth: OAuth 2.0
• Scopes: api, read_user
• Enables: gitlab.projects, gitlab.issues, gitlab.merge_requests

Jira

• Auth: API token (Atlassian Cloud) / OAuth 2.0 (Atlassian Connect)
• Enables: jira.search, jira.get_issue, jira.create_issue, jira.list_projects, jira.transition_issue
• Notes: API token is faster to set up. OAuth required for third-party marketplace-style integrations.

Confluence

• Auth: API token (Cloud)
• Enables: confluence.search, confluence.get_page, confluence.create_page, confluence.update_page, confluence.list_spaces, confluence.add_comment

Linear

• Auth: API key
• Enables: linear.issues, linear.create_issue, linear.search, linear.update_issue

Collaboration

Slack

• Auth: OAuth 2.0 (Bot + User scopes)
• Scopes: chat:write, channels:read, channels:history, users:read, files:write
• Enables: Channel adapter (Slack channel), plus slack.post_message, slack.search, slack.upload_file

Discord

• Auth: Bot Token
• Enables: Channel adapter (Discord channel), discord.post_message, discord.create_thread

Microsoft Teams

See Microsoft section above.

Signal

• Auth: signal-cli bridge
• Enables: Channel adapter only (Signal channel)

Matrix

• Auth: Matrix access token
• Enables: Channel adapter (Matrix channel)

WhatsApp (Business Cloud API)

• Auth: Meta Business Cloud API access token
• Enables: Channel adapter (WhatsApp channel)

Notes & docs

Notion

• Auth: OAuth 2.0
• Enables: notion.search, notion.get_page, notion.create_page, notion.update_page, notion.query_database

Obsidian (filesystem)

• Auth: Filesystem MCP server pointed at your vault
• Enables: read/write Markdown files under your vault folder
• Notes: Not a native connector — use the Filesystem MCP server (see MCP Client).

Tasks & productivity

Todoist

• Auth: API token
• Enables: todoist.tasks, todoist.create_task, todoist.complete_task, todoist.projects

Asana

• Auth: OAuth 2.0
• Enables: asana.tasks, asana.create_task, asana.update_task, asana.projects

Trello

• Auth: OAuth 1.0a
• Enables: trello.boards, trello.cards, trello.create_card

Messaging / SMS

Twilio

• Auth: Account SID + Auth Token
• Enables: sms.send, sms.inbox
• Notes: SMS channel adapter uses this (SMS channel). Twilio is an SMS connector only — Sophon does not place phone calls.

Telnyx

• Auth: API key
• Enables: sms.send (alternative to Twilio)

Storage

Dropbox

• Auth: OAuth 2.0
• Enables: dropbox.list, dropbox.upload, dropbox.download, dropbox.search

Box

• Auth: OAuth 2.0 (JWT for service accounts)
• Enables: box.list, box.upload, box.download

CI / DevOps (roadmap)

Sentry, Datadog, PagerDuty, Grafana, Prometheus

• Status: Official connectors on the roadmap (P1).
• Today: use the HTTP skill or a dedicated MCP server for these.

LLM providers

These are configured in Settings → Models, which uses the same credential vault as Connections. Listed here for completeness:

Speech providers

Speech providers are configured in Settings → Voice (Voice Center), not under Connections, and their keys go into the same credential vault. Nothing is preconfigured: voice works with no provider at all, using the browser's or device's own speech. See Voice Providers.

Six text-to-speech providers:

Six speech-to-text providers:

Deepgram is the only streaming speech-to-text provider; the other five transcribe the whole utterance after you stop. Hands-free works with all six either way — Sophon supplies the end-of-speech detection for the ones that can't.

Adding a custom connector

Any service not in this list can be integrated via:

1. HTTP skill — if the service has a REST API, author a skill that calls it (manual or via skill.author).
2. MCP bridge — if an MCP server exists for the service, register it as a client-side MCP connection.
3. Plugin — for deeper integration (custom channel adapter, custom vault backend, custom model provider), write a .NET plugin — see DevStudio.

Notes on scopes

Every OAuth connector requests minimum scopes necessary. Upgrading scopes requires re-authenticating — you'll see a new consent screen. This is a deliberate security choice: you always see what you're granting, every time scopes change.

If a connector is missing a scope you need (e.g., Gmail forwarding_addresses), file an issue. We don't add scopes silently.

Where to go next

• Connections — the mechanics of adding, testing, and revoking
• Skills — which skills each connection unlocks
• MCP Client — extend beyond the native catalog