Curiosity

Built-in integrations

Curiosity Workspace ships with packaged connectors for the most common SaaS systems. Each integration handles its own OAuth or credential flow, schema registration, delta sync, and access-control mapping. Configure them from Manage → Integrations in the workspace UI.

The pages in this section describe what each integration ingests, how it authenticates, and how the source system's permissions map onto the workspace graph.

flowchart TB subgraph Sources [Source systems] Cloud[Cloud storage] Email[Email] Cal[Calendars] Chat[Chat / messaging] KB[Knowledge bases] IT[Issue tracking] CRM[CRM / business apps] Web[Web / feeds] end subgraph WS [Curiosity Workspace] AG[Access groups] Graph[(Graph)] Idx[Search index] end Cloud -->|files| Graph Email -->|messages + attachments| Graph Cal -->|events| Graph Chat -->|messages + members| Graph KB -->|pages + notes| Graph IT -->|issues + PRs| Graph CRM -->|contacts + deals| Graph Web -->|articles| Graph Cloud -.->|per-item ACL| AG Chat -.->|channel membership| AG IT -.->|project roles| AG AG --> Graph Graph --> Idx

At-a-glance comparison

Category Integrations OAuth Maps source ACLs Incremental sync
Cloud storage 10 mostly yes deltas / cursors / change tokens
Email 5 OAuth where available per-user history IDs / delta links / UIDVALIDITY
Calendar 2 yes per-user per-calendar delta tokens
Chat & messaging 2 yes per channel / team delta + timestamp tracking
Knowledge bases 3 yes per-user USN / latest_update / connector version
Issue tracking 2 yes yes (project roles) updated watermarks
CRM & business apps 4 mostly partial LatestFetchedUpdates / object timestamps
Web & feeds 4 n/a public polling on cron

Authentication options

flowchart LR User([User]) -->|click 'Connect'| WS[Workspace] WS --> Pick{Auth type?} Pick -->|OAuth| Provider[Provider's consent screen] Pick -->|API token| Form[Token form] Pick -->|User + password| Creds[Credentials form] Provider -->|access + refresh token| Store[(Encrypted secrets)] Form --> Store Creds --> Store Store --> Connector[Scheduled connector run]

OAuth providers (Google, Microsoft Graph, Dropbox, Box, Slack, GitHub, HubSpot, Notion, Salesforce, Zendesk, Atlassian, Yahoo, Evernote, pCloud) are handled centrally — Curiosity exchanges the OAuth code, stores the refresh token encrypted, and re-runs the refresh flow before access tokens expire. Token expiry surfaces in the UI as a per-user re-auth prompt.

For credential-based integrations (IMAP, POP3, FTP, Airtable, S3, Azure Storage), the user provides the secret directly. Secrets are encrypted at rest.

Browse by category

Cloud storage

S3, Azure Blob, Box, Dropbox, FTP, Google Drive, OneDrive, SharePoint, pCloud.

Email

Gmail, Microsoft Outlook, IMAP, POP3, Yahoo.

Calendar

Google Calendar, Microsoft Outlook Calendar.

Chat & messaging

Slack, Microsoft Teams.

Knowledge bases

Confluence, Evernote, Notion.

Issue tracking

GitHub, Jira.

CRM & business apps

Airtable, HubSpot, Salesforce, Zendesk.

Web & feeds

RSS, Web Crawler, Hacker News, XKCD.