Connectors

Connectors and Endpoints are used to bring data into Curiosity systems and programatically interact with the system.

Curiosity Architecture

Overview

Connectors interface with various data sources like databases, APIs, or file systems, extracting data and importing it into Curiosity. Each connector is tailored to a specific type of data source, responsible for retrieving data and transforming it into a compatible format for Curiosity.

Bi-directional: Connectors can be bi-directional, i.e. they can feed data back from Curiosity to the data source. For example, a bi-directional connector is used by the integrated email client to manage emails on the email server.

Hosting: Connectors can be hosted inside the Curiosity workspace for simplicity, or in separate systems (e.g. if the server can't talk directly to the data sources).

Scheduling: Connectors can be run as scheduled jobs or the server can listen for events (changes in the data sources).

Access control: Connectors are also responsible for communicating access permissions from the data source to Curiosity. That can use standard permissions models, e.g. Microsoft Graph, or custom access permissions in a custom connector. Learn more about permissions and configuring access control.

Standard connectors

By default, Curiosity includes connectors for a range of data sources including common cloud storage, email programs, and others. You can find the current list of integrations for the desktop app here. Additional integrations for Server workspaces are shown in the admin UIs.

API connectors

You can write custom connectors for your own data sources. These map the data from the source into the Curiosity system.

Learn more about API integrations.

Outgoing APIs (Endpoints)

API endpoints allow you to interact programatically with the Curiosity Workspace. You can use them to extract data or to call functions on the server (e.g. post a search query and receive a list of results). Standard APIs are available as part of the system. In addition, you can write custom APIs.

Learn more about API endpoints.