Connect your apps

Your work doesn’t all start in Snoze — it lives in chat threads, issue trackers, and drives. Connections bring those tools in, so their content shows up next to your pages and databases instead of in another tab.

Snoze connects to Slack, Google Workspace, Microsoft 365, GitHub, Linear, Jira, and Notion.

What connecting does

• Sync data in — pull records from the service into your workspace on a schedule, where they behave like external data: queryable, chartable, always current.
• Browse and link resources — attach files, documents, and issues from the connected service to your pages and items, without re-uploading anything.
• Give the assistant reach — once connected, the assistant can pull from those sources when you ask about your work.

Connect a service

1. Open Connections

   Go to workspace settings and open the Connections section. Each provider shows whether it’s connected and who connected it.

2. Authorize with the provider

   Pick a service and sign in with it. You approve the access in the provider’s own consent screen — Snoze asks only for the scopes it uses, and you can review them there before agreeing.

3. Choose what comes in

   Pick what to sync or browse — the channels, projects, or folders that matter. You can change this any time, and disconnecting removes access immediately.

Where the data shows up

Synced data lands in your workspace like a database: point widgets at it, filter it into views, and mix it with native data on one dashboard. Linked resources appear on the items you attach them to, with live previews where the provider supports them.

GitHub repositories

Connecting GitHub goes a step further than syncing rows: a repository opens as a full surface inside Snoze, tabbed across everything you’d go to GitHub for.

• Code — browse the repo’s file tree and read files with syntax highlighting.
• Pull requests — read a PR’s conversation and its diff (unified or split, highlighted like every other code surface), and merge, close, or comment without leaving Snoze.
• Issues — read, comment, close, and reopen.
• Branches — inspect branches and a commit graph, and open any commit’s diff.
• Data — the issues and pull requests that sync into a workspace database, with their sync health.

Repository management flows one way — from GitHub, changes push back through the management actions above; there’s no two-way row sync. The rest is exactly the integration model described here, with no GitHub-specific setup beyond authorizing the connection.

Working the other direction — letting AI clients and your own code reach into Snoze — is covered in Set up the MCP server and API keys and scopes.