Skip to main content
connections give pipes and AI agents structured context from the source system, beyond what screenpipe can infer from visible app text. screenpipe privacy settings

​
finding credentials

when setting up connections that require API keys, credentials, or URLs, screenpipe provides direct help links in the settings UI:
  • look for the ? icon next to each field (API Key, Webhook URL, etc.)
  • hover or click to see “Learn how to find your X for this integration”
  • select Open guide → to jump to that service’s settings or API docs page
  • no more hunting through documentation
this works for all API key, webhook, and custom credential fields.

​
auth patterns

​
credential storage

screenpipe stores connection credentials in the local secure store when available. environments without the secure store can fall back to ~/.screenpipe/connections.json. pipe prompts should not contain secrets. prefer connected app proxies:
screenpipe injects the credential on the local side, so the AI sees the request shape but not the secret value.

​
available integrations

The app registry currently includes these connection IDs:

​
multi-account support

use named instances when you have more than one account for the same service: Composio-managed integrations (Gmail, Zoom, Google Drive/Docs/Sheets) also support multiple accounts: use connect another account on the integration card and give each account a label (for example work, personal). Up to 5 accounts per integration. The AI uses the most recently connected account by default and targets a specific one when you name it (“check my work gmail”).

​
test queries

after connecting, run a tiny request before relying on a pipe:
Email Inbox (IMAP) is not proxied (IMAP is not HTTP) — use its dedicated read-only endpoints: /connections/imap/messages, /connections/imap/messages/{uid}, and /connections/imap/mailboxes. exact provider paths follow the provider API. if a request fails, reconnect the integration first, then check the provider’s own permissions.

​
OAuth callback troubleshooting

OAuth redirects back to:
if OAuth fails:
  1. keep screenpipe open during the login flow.
  2. check curl http://localhost:3030/health.
  3. make sure the browser did not block the redirect.
  4. reconnect from settings -> connections.
  5. check whether the provider account type is supported. Microsoft Teams, for example, needs a work or school account.

​
choosing the right connection