Feeds

Graphlit connects to 35 data sources with automatic sync. OAuth, API keys, or public sources.

API terminology: In the Graphlit API, these are called feeds (you create them with createFeed()).

Feed = A connection that continuously syncs data from a source (Slack, S3, RSS, etc.) Connector = Optional per-user auth credential storage (smaller, used with feeds)

Authentication: Feeds support OAuth (Slack, Gmail), API keys (S3, Tavily), or public access (RSS, web crawls).


How Feeds Work

No manual uploads

Set up once, content syncs automatically

Configurable polling

Schedule policies from 30 seconds to hours between checks

OAuth handled

No token management, Graphlit handles auth refresh

Incremental updates

Only new/changed content syncs (not full re-ingest)

Deduplication

Same file in Slack and Drive = one copy in your knowledge base


All Feeds (35)

Cloud Storage (4)

Amazon S3

Files from any S3 bucket Access Key auth • Automatic sync

Azure Blob Storage

Files from Azure containers Connection String auth • Automatic sync

Azure File Share

Files from Azure file shares Connection String auth • Automatic sync

Google Cloud Storage

Files from GCS buckets Service Account auth • Automatic sync

Use cases: Data lakes, backup archives, media libraries, log files

Example:


User Storage & Productivity (5)

Microsoft SharePoint

Files and pages from SharePoint sites OAuth (Microsoft) • Automatic sync

Microsoft OneDrive

Personal and business files OAuth (Microsoft) • Automatic sync

Google Drive

Files, Docs, Sheets, Slides OAuth (Google) • Automatic sync

Dropbox

All file types OAuth (Dropbox) • Automatic sync

Box

Enterprise file storage OAuth (Box) • Automatic sync

Use cases: Company knowledge base, shared documentation, team collaboration, project resources

Example:


Communication & Messaging (4)

Slack

Messages, threads, files from channels OAuth (Bot Token) • Automatic sync

Microsoft Teams

Messages from team channels OAuth (Microsoft) • Automatic sync

Discord

Messages, threads, files from servers OAuth (Bot Token) • Automatic sync

Twitter/X

Posts, media, conversations OAuth (Twitter API) • Automatic sync

Use cases: Team conversations, decision history, customer discussions, product feedback

Example:


Email (2)

Gmail

Emails, attachments, labels, threads OAuth (Google) • Automatic sync

Microsoft Outlook

Emails, attachments, folders OAuth (Microsoft) • Automatic sync

Use cases: Customer communications, sales outreach, support context, contract negotiations

Example:


Issue Tracking & Project Management (6)

Linear

Issues, comments, projects, roadmaps OAuth (Linear API) • Automatic sync

Jira

Issues, comments, boards, sprints OAuth (Atlassian) • Automatic sync

GitHub Issues

Repository issues and comments OAuth (GitHub) • Automatic sync

GitHub Commits

Repository commits and code changes OAuth (GitHub) • Automatic sync

GitHub Pull Requests

Pull requests and code reviews OAuth (GitHub) • Automatic sync

Trello

Cards, boards, checklists OAuth (Trello API) • Automatic sync

Use cases: Product roadmaps, bug tracking, feature requests, sprint planning

Example:


Knowledge Bases & Documentation (3)

Connector
Content Types
Auth Type
Sync Mode

Notion

Pages, Databases

OAuth (Notion API)

Automatic

Intercom Articles

Articles

OAuth (Intercom)

Automatic

Zendesk Articles

Articles

OAuth (Zendesk)

Automatic

Use cases:

  • Internal wikis

  • Product documentation

  • Help center content

  • Company policies

Example:


Support & Ticketing (2)

Connector
Content Types
Auth Type
Sync Mode

Intercom Tickets

Tickets, Conversations

OAuth (Intercom)

Automatic

Zendesk Tickets

Tickets, Conversations

OAuth (Zendesk)

Automatic

Use cases:

  • Customer support history

  • Common issues

  • Product feedback

  • Feature requests


Code Repositories (1)

Connector
Content Types
Auth Type
Sync Mode

GitHub

Code Files, README

OAuth (GitHub PAT)

Automatic

Use cases:

  • Code search

  • Documentation in repos

  • README indexing

  • API references

Example:


Web & Content (6)

Connector
Content Types
Auth Type
Sync Mode

Web Pages

Pages, Files

None

On-demand / Scheduled

Web Search

Search Results

None

On-demand

RSS Feeds

Posts, Articles

None

Automatic

Podcast RSS

Audio, Transcripts

None

Automatic

YouTube

Audio (transcribed)

API Key (optional)

On-demand

Reddit

Posts, Comments

API Key (optional)

Automatic

Use cases:

  • Competitive intelligence

  • News monitoring

  • Content aggregation

  • Market research

Example:


Calendars (2)

Connector
Content Types
Auth Type
Sync Mode

Google Calendar

Events

OAuth (Google)

Automatic

Microsoft Calendar

Events

OAuth (Microsoft)

Automatic

Use cases:

  • Meeting recording triggers

  • Event-based workflows

  • Schedule context

  • Attendee tracking

Example:


Feed Sync Modes

Real-Time Sync (ARCHIVE)

Default mode: Preserve everything, never delete

Behavior:

  • New content added

  • Updated content re-indexed

  • Deleted content at source → preserved in Graphlit

  • Use case: Compliance, audit logs, historical research


Mirror Sync (SYNC)

Mirror mode: Keep in sync with source

Behavior:

  • New content added

  • Updated content re-indexed

  • Deleted content at source → deleted in Graphlit

  • Use case: Live documentation, current state only


OAuth Setup

Graphlit Manages OAuth

You don't need to:

  • ❌ Store refresh tokens securely

  • ❌ Handle token expiration

  • ❌ Implement refresh logic

  • ❌ Manage webhook subscriptions

Graphlit handles:

  • ✅ Token storage (encrypted)

  • ✅ Automatic refresh

  • ✅ Webhook management

  • ✅ Error recovery

Setup Process

  1. Get OAuth credentials from provider (e.g., Google Cloud Console, Microsoft Azure Portal)

  2. Exchange for refresh token (one-time)

  3. Pass to Graphlit when creating feed

  4. Done - Graphlit manages tokens forever

See: OAuth Setup Guide for detailed instructions per provider.


Feed Filters

Filter by Query (Gmail, Slack, etc.)

Filter by Folder/Channel

Filter by Time


Common Patterns

Pattern 1: Multi-Source Customer View


Pattern 2: Developer Knowledge Base


Pattern 3: Compliance Archive


Real-World Example: Zine

Zine uses 20+ Graphlit connectors:

Connected sources:

  • Slack, Teams, Discord

  • Gmail, Outlook

  • Google Drive, OneDrive, Dropbox

  • Notion, Linear, Jira

  • GitHub Issues

  • Google Calendar, Microsoft Calendar

  • Meeting recordings (auto-attached to calendar events)

Result:

  • One search across all tools

  • AI agents with full company context

  • Meeting intelligence

  • Customer interaction history

  • Developer knowledge base

All powered by Graphlit connectors.


Connector Roadmap

Coming soon (upon request):

  • Confluence

  • Salesforce

  • ServiceNow

  • Azure Repos

  • Zoom (meeting recordings)

  • Google Meet (meeting recordings)

  • Azure Boards

Want a connector? Request it in Discord


Next Steps


Connect once. Search forever.

Last updated

Was this helpful?