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
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 workspacenotion:personal— your personal workspace
Use connections from scheduled tasks
Connections can expose a local proxy endpoint so scheduled tasks can call third-party APIs without putting secrets in the prompt:AI tool connections (MCP)
These are different from app connections — they let you use Screenpipe’s data inside external AI tools:Why connect apps?
Without connections, Screenpipe captures what’s visible on your screen. With connections, scheduled tasks get structured data directly from the source:
This makes scheduled tasks 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:- On the Google warning screen, click Advanced (bottom-left corner)
- Click Go to Screenpipe (unsafe) to continue with the connection
- Screenpipe will not be marked unsafe once you verify the connection — this is a standard OAuth security flow
- 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 scheduled tasks
If a scheduled task 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 scheduled task is using the correct instance name (e.g.,
notion:workvsnotion:personal) - Try reconnecting: disconnect and reconnect the app
- Check the scheduled task debugging guide for troubleshooting task-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
Grok Bot
To connect Grok Bot (also searched as grokbot), open Settings → Connections, choose Grok Bot, and click connect Grok Bot. Keep Grok Bot installed, signed in, and running on this computer. The explicit connection installs Screenpipe skills using Grok Bot’s saved connection credential; it is not connected automatically. Keep both apps open. Ask Grok Bot to search a harmless phrase recorded in the last five minutes, and verify the returned app and timestamp. Retrieval uses Grok Bot’s approved access to this local computer. A cloud computer’slocalhost is not your recorder, and an installed skill alone does not prove retrieval works.
Results you request are shared with Grok Bot. If local-computer access is unavailable, report that gap instead of opening a public tunnel or disabling API authentication. Use repair connection for a stale installation. A cached status or a local disconnect does not confirm remote installation or removal.