> ## Documentation Index
> Fetch the complete documentation index at: https://docs.screenpipe.com/llms.txt
> Use this file to discover all available pages before exploring further.
# connection reference: auth, proxies, and credentials
> Reference for screenpipe app connections: available integrations, auth style, proxy usage, multi-account support, credential storage, and test queries.
{/* https://screenpi.pe */}
connections give pipes and AI agents structured context from the source system, beyond what screenpipe can infer from visible app text.
## 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
| pattern | examples | notes |
| -------------------------- | ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| OAuth | Outlook, Google Calendar, Google Docs, Notion, Jira, Microsoft 365, Teams, Vercel, Supabase, Zoom, HubSpot | best user experience; tokens are stored locally; no API key needed |
| API key | Linear, PostHog, Sentry, Stripe, Toggl, Pipedrive, Glean, Mochi | simple and reliable; help links guide you to API settings pages; rotate keys if a device is lost |
| webhook URL | n8n, Make, Zapier, Pushover, ntfy, Resend | best for one-way notifications or workflow triggers |
| app password | Email Inbox (IMAP) | read-only inbox access without OAuth; for Gmail, create one at myaccount.google.com/apppasswords (requires 2-Step Verification) |
| local path | Obsidian, Logseq | keeps notes local |
| custom/private CA | Bee | screenpipe includes the required trust configuration for the provider |
| managed OAuth via Composio | Gmail, Zoom, Google Drive, Google Docs, Google Sheets | one-click sign-in managed by composio.dev (SOC 2), available on every plan. Sign-in and data access run through Composio's cloud, and the agent reaches these through the shared Composio MCP server (sp\_mcp tools), not the connection proxy |
## 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:
```bash theme={null}
curl "http://localhost:3030/connections//proxy/"
```
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:
| category | integrations |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| communication | Slack, Discord, Email (SMTP), Email Inbox (IMAP), Gmail (via Composio), Outlook, Telegram, WhatsApp, Microsoft Teams, Zoom (via Composio) |
| productivity | Notion, Obsidian, Google Calendar, Google Docs, Google Drive (via Composio), Google Sheets (via Composio), Microsoft 365, Logseq, Workflowy, Airtable, Confluence, Odoo, Mochi, Hermes |
| project management | Linear, Jira, Asana, Monday.com, Trello, ClickUp, Todoist, Cal.com, Calendly |
| CRM and support | HubSpot, Salesforce, Pipedrive, Intercom, Zendesk, Bitrix24 |
| developer and ops | GitHub, Sentry, Vercel, Supabase, PostHog |
| finance | Stripe, Brex, QuickBooks Online, Financial Sense |
| meeting and voice | Granola, Fireflies.ai, Otter.ai, Limitless, Bee, Pocket, Lexi AI |
| automation and notifications | n8n, Make, Zapier, Pushover, ntfy, Loops, Resend |
| AI and knowledge | Perplexity, Glean, Readwise |
| AI assistant memory | Claude Code, Codex CLI, Obsidian Memories |
| AI agent gateway | OpenClaw |
## multi-account support
use named instances when you have more than one account for the same service:
| example | use |
| ----------------------------------------------------- | ------------------------------------- |
| `notion:work` and `notion:personal` | separate work and personal workspaces |
| `google-calendar:work` and `google-calendar:personal` | separate calendars |
| `hubspot:prod` and `hubspot:sandbox` | separate CRM portals |
| `posthog:screenpipe` and `posthog:bench` | separate analytics projects |
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:
```bash theme={null}
curl "http://localhost:3030/connections/google-calendar/events?hours_ahead=8"
curl "http://localhost:3030/connections/notion/proxy/v1/users/me"
curl "http://localhost:3030/connections/hubspot/proxy/crm/v3/objects/contacts?limit=1"
curl "http://localhost:3030/connections/linear/proxy/graphql"
curl "http://localhost:3030/connections/readwise/proxy/api/v2/auth/"
curl "http://localhost:3030/connections/imap/messages?limit=5"
```
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:
```text theme={null}
http://localhost:3030/connections/oauth/callback
```
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
| need | connect |
| ---------------------------- | --------------------------------------- |
| better speaker names | Google Calendar |
| CRM follow-up after calls | HubSpot, Salesforce, Pipedrive, Notion |
| daily notes and highlights | Obsidian, Logseq, Google Docs, Readwise |
| product analytics context | PostHog, Sentry, GitHub, Vercel |
| finance or billing workflows | Stripe, Brex, QuickBooks |
| meeting import | Zoom, Fireflies.ai, Granola, Otter.ai |
| notifications | Slack, Pushover, ntfy, Resend |
## related pages
* [connections](/connections)
* [pipe debugging](/pipe-debugging)
* [meeting intelligence](/meeting-intelligence)
* [privacy data flow](/privacy-data-flow)