Skip to main content
Connections give scheduled tasks 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. Scheduled task 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 scheduled task:
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