Verida AI Docs
  • Welcome
  • Getting Started
    • How it works
    • Developer Console
    • Get an API key
    • Authentication
    • Scopes
    • API Requests
    • Connectors
      • Build a Connector
    • Example Apps
  • Integrations
    • PersonalAgentKit
    • LangGraph
    • NEAR Protocol
    • Nillion Network
  • Data APIs
    • Overview
    • Data Types
    • API Endpoints
      • Queries
      • Search
      • AI Prompts
      • Actions
      • Other Endpoints
    • API Performance
    • Data examples
    • API Reference
  • Resources
    • Tutorials
      • Accessing User Data (Telegram)
    • Learn
      • Anatomy of an AI Agent
      • Dynamic Loading of Data for Realtime AI
      • Data Privacy Issues
      • Web3 & DePIN solves AI's privacy problems
      • Privacy Preserving AI Tech Stack
      • Confidential Compute Litepaper
    • AI Use Cases
    • Verida Vault
    • Privacy & Security
    • Pricing
    • Grants
    • Support
Powered by GitBook
On this page
  • Supported Connectors
  • In Development Connectors
  • Connection Framework
  • Connection Handlers
  • Request a Connector
  • Fetching Historical Data
Export as PDF
  1. Getting Started

Connectors

PreviousAPI RequestsNextBuild a Connector

Last updated 3 months ago

Users can connect multiple data sources to their Verida account via the . Data is syncronized on demand and stored to the user's encrypted databases on the .

Looking to build your own connector? See our getting started guide.

Supported Connectors

  1. Google

    1. Gmail

      1. Email

    2. Google Calendar

      1. Calendars

      2. Events

    3. Google Drive

      1. Files

    4. Youtube

      1. Following

      2. Likes

      3. Subscriptions

      4. Posted Videos

  2. Telegram

    1. Groups

    2. Messages

In Development Connectors

  1. Notion

  2. Slack

  3. Facebook

  4. Fireflies

  5. Spotify

Connection Framework

Verida's Data Connections framework makes it easy for users to connect and pull their personal data from platforms like Google, Telegram, or Facebook into their private storage. The framework facilitates tasks like signing in, verifying access, and syncing user data from these centralized platforms.

Connection Handlers

Connections (ie: Google) have multiple handlers (ie: Gmail, Calendar etc.) that process different types of data available for a given connection. These handlers typically require specific permission to be granted when authorizing the connection. For example; A user will need to permit Verida access to the "Calendar" otherwise that data won't synchronize.

Handlers have built-in options specific to their functionality. For example; The Telegram handler has an option to only sync groups with less than 50 participants.

Handler options are currently implemented in the backend and will be made available in the user interface soon.

Request a Connector

You can request a new connector via our roadmap here:

Fetching Historical Data

The default setting for all handlers is to fetch data up to 3 months old. In the future users will be able to customize this to increase the historical data to fetch. This will obviously increase the amount of data storage and memory usage for that user's data.

You can view a list of completed, in progress and planned connectors in the

The Verida Data Connection framework source code is open source and . A full list of connectors can be found in the .

Verida Vault
Verida Network
Build a Connector
Connectors Roadmap
available on GitHub
providers folder
https://roadmap.verida.ai/data-connectors