Documentation Index
Fetch the complete documentation index at: https://docs.screenpi.pe/llms.txt
Use this file to discover all available pages before exploring further.
connections give pipes and AI agents structured context from the source system, beyond what screenpipe can infer from visible app text.
auth patterns
| pattern | examples | notes |
|---|
| OAuth | Gmail, Google Calendar, Google Docs, Notion, Jira, Microsoft 365, Teams, Vercel, Supabase, Zoom | best user experience; tokens are stored locally |
| API key | Linear, HubSpot, PostHog, Sentry, Stripe, Toggl, Pipedrive, Glean | simple and reliable; rotate keys if a device is lost |
| webhook URL | n8n, Make, Zapier, Pushover, ntfy, Resend | best for one-way notifications or workflow triggers |
| local path | Obsidian, Logseq | keeps notes local |
| custom/private CA | Bee | screenpipe includes the required trust configuration for the provider |
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:
curl "http://localhost:3030/connections/<id>/proxy/<provider-path>"
available integrations
The app registry currently includes these connection IDs:
| category | integrations |
|---|
| communication | Slack, Discord, Email (SMTP), Gmail, Telegram, WhatsApp, Microsoft Teams, Zoom |
| productivity | Notion, Obsidian, Google Calendar, Google Docs, Google Sheets, Microsoft 365, Logseq, Airtable, Confluence |
| 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 |
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 |
gmail:founder and gmail:support | separate inboxes |
hubspot:prod and hubspot:sandbox | separate CRM portals |
posthog:screenpipe and posthog:bench | separate analytics projects |
test queries
after connecting, run a tiny request before relying on a pipe:
curl "http://localhost:3030/connections/gmail/proxy/users/me/profile"
curl "http://localhost:3030/connections/google-calendar/proxy/users/me/calendarList"
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"
OAuth callback troubleshooting
OAuth redirects back to:
http://localhost:3030/connections/oauth/callback
- keep screenpipe open during the login flow.
- check
curl http://localhost:3030/health.
- make sure the browser did not block the redirect.
- reconnect from settings -> connections.
- 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 | Obsidian, Logseq, Google Docs |
| 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