Skip to main content
screenpipe captures your screen and audio by default. but you can also connect your apps directly — this gives pipes and AI agents richer, structured data from the source.
for the complete registry, auth patterns, multi-account examples, and proxy test calls, use the connection reference.

​
how to connect apps

open screenpipe → click settings (gear icon, bottom of sidebar) → scroll to Data & Privacy → click Connections. you’ll see all available integrations. click one to configure credentials or start an OAuth flow.

​
finding API keys & credentials

for integrations that require API keys or other credentials, screenpipe provides help links next to each field:
  • look for the ? icon next to the field label (e.g., “API Key”)
  • hover over it to see “Learn how to find your API Key for this integration”
  • click Open guide → to jump directly to that app’s settings page
this takes you straight to where you need to be — no more hunting through docs. oauth integrations (Slack, Notion, Google Calendar, etc.) skip the API key step entirely — just click the big “Connect with [App]” button and approve access in your browser.
some pipes require specific connections. when you install a pipe that needs a connection (like Notion or Toggl), screenpipe will prompt you to configure it automatically.

​
available integrations

this is a quick reference of common integrations. for the complete, canonical list of every supported integration — with auth style, proxy paths, and multi-account examples — see the connection reference.

​
communication

​
productivity & project management

​
CRM & sales

​
calendar & scheduling

​
developer tools

​
automation platforms

​
time tracking

​
notifications

​
AI & knowledge

​
other

​
multi-account support

you can connect multiple accounts for the same app using instance names. for example, connect both your work and personal Notion:
  • notion:work — your company workspace
  • notion:personal — your personal workspace
this is configured in the connections UI when adding a new integration.

​
use connections from pipes

connections can expose a local proxy endpoint so pipes can call third-party APIs without putting secrets in the prompt:
see connection reference and pipe debugging for safe proxy patterns.

​
AI tool connections (MCP)

these are different from app connections — they let you use screenpipe’s data inside external AI tools:
you can use both app connections AND AI tool connections at the same time. connect Google Calendar + Obsidian as data sources, AND connect Claude Desktop to query everything.

​
why connect apps?

without connections, screenpipe captures what’s visible on your screen. with connections, pipes get structured data directly from the source: this makes pipes significantly more accurate and useful.

​
troubleshooting

​
Google OAuth: “app isn’t verified” or “unsafe”

when connecting Google Calendar or Google Docs, you may see a warning that says the app is “unverified” or “unsafe.” this is normal — screenpipe is a local app and Google requires additional verification steps for third-party apps. how to proceed:
  1. on the Google warning screen, click Advanced (bottom-left corner)
  2. click Go to Screenpipe (unsafe) to continue with the connection
  3. screenpipe will not be marked unsafe once you verify the connection — this is a standard OAuth security flow
if the page closes or doesn’t load, check that:
  • you have internet connectivity
  • no browser extensions are blocking the OAuth redirect
  • your firewall isn’t blocking localhost:3030 (the local callback endpoint)

​
connection fails silently

if a connection appears to connect but then disappears:
  • check that Pro is active (OAuth requires a Pro subscription)
  • verify the app credentials are correct by disconnecting and reconnecting
  • check app permissions in the original service (e.g., Notion workspace settings, Slack workspace admin console) — you may need to re-approve access

​
”not connected” error in pipes

if a pipe reports that a connection isn’t available:
  • confirm the connection is active in settings → connections (green dot or “connected” status)
  • for multi-account setups, verify the pipe is using the correct instance name (e.g., notion:work vs notion:personal)
  • try reconnecting: disconnect and reconnect the app
  • check the pipe debugging guide for troubleshooting pipe-specific issues

​
privacy & security

  • OAuth connections use standard OAuth flows — screenpipe stores tokens locally in your secure store when available
  • CLI-like environments can fall back to local ~/.screenpipe/connections.json
  • connected app data stays on your device
  • you can disconnect any app at any time in settings → connections
  • screenpipe never sends your connected app data to our servers
  • OAuth connections require a Pro subscription
questions? join our discord.