Providers
Index Lane works because it stays honest about provider differences.
The goal is not to flatten every provider into one fake model. The goal is to make the result surface consistent while still respecting how each provider actually works.
Provider matrix
| Provider | Native search/input model | Saved access rule options | Typical item returned |
|---|---|---|---|
| Notion | Shared workspace content available through the integration | all or selected page/database ids | Page |
| Google Drive | Drive file and folder metadata plus provider-native filtering | all or selected folders/shared drives/files | File |
| Gmail | Gmail search syntax and Gmail label semantics | all, recent, labels, or query | Thread or message hit |
| Google Calendar | Calendar list plus event retrieval | all or selected calendar ids | Event |
Notion
What Index Lane uses
- the Notion integration grant
- pages and databases visible to that integration
Access model
allselectedIds
Use selectedIds when you want Index Lane scoped to known pages or databases instead of the entire connected workspace surface.
Result behavior
Notion results usually work best when title and recent page context line up. Index Lane preserves the Notion source type and source URL so you can see exactly what page or database entry matched.
Google Drive
What Index Lane uses
- files
- folders
- shared drives when available
Access model
all- selected
folderIds - selected
sharedDriveIds - selected
fileIds
Result behavior
Drive results are best when the user has already narrowed the surface. If you leave Drive wide open, the result set can get noisy quickly, especially in large shared workspaces.
Gmail
What Index Lane uses
- Gmail-native query behavior
- Gmail labels
- Gmail recency filters
Access model
allrecentlabelsquery
Examples:
{"mode":"recent","recentDays":30}{"mode":"labels","labelIds":["IMPORTANT","INBOX"]}{"mode":"query","q":"label:important newer_than:30d"}
Result behavior
Gmail is intentionally label- and query-driven. Index Lane does not invent a fake folder abstraction on top of Gmail because Gmail is not really a folder-first system.
Google Calendar
What Index Lane uses
- connected calendars
- calendar events
Access model
all- selected
calendarIds
Result behavior
Calendar results are naturally time-oriented. Recency and event timing matter more here than in most other providers, so Index Lane keeps event timestamps and calendar provenance explicit.
Design principle
Index Lane normalizes result output, not provider identity.
That is why every hit still tells you:
- what provider produced it
- what account it came from
- what item type it is
- what source URL or id maps back to the provider