Overview
What Gets Indexed
| Source | Content |
|---|---|
| Files | Text, documents, and other extractable file content from configured directories |
| Metadata | File name, path, size, and modification timestamps |
How It Works
- You provide a Nextcloud server URL, username, and app password
- The connector walks the configured directory tree via WebDAV
PROPFIND - Full and incremental syncs use ETag-based change detection
- Removed files are detected automatically on each sync
- Extension allow/deny lists and a max file size filter control what gets indexed
The connector uses read-only WebDAV access — it cannot modify or delete any files in your Nextcloud instance.
Prerequisites
Before setting up the Nextcloud connector, ensure you have:- Nextcloud instance reachable from the Omni network
- A Nextcloud user account with read access to the directories you want to index
- Omni deployment with the Nextcloud connector service running (profile:
nextcloud)
Setup
Step 1: Create an App Password
- Sign in to Nextcloud as the user Omni will connect as
- Go to Settings → Security → Devices & sessions
- Enter a name (e.g.
omni) and click Create new app password - Copy the generated password — it will not be shown again
Step 2: Connect in Omni
- Navigate to Settings → Integrations in Omni
- Find Nextcloud and click Connect
- Enter the connection details:
- Server URL: Your Nextcloud instance (e.g.
https://cloud.example.com) - Username: The Nextcloud username
- App Password: The app password from Step 1
- Server URL: Your Nextcloud instance (e.g.
- Optionally configure advanced settings:
| Setting | Default | Description |
|---|---|---|
base_path | / | Subdirectory to sync (e.g. /Shared/Engineering) |
extension_allowlist | all | Only sync files with these extensions |
extension_denylist | none | Skip files with these extensions |
max_file_size | 0 (unlimited) | Maximum file size in bytes |
sync_enabled | true | Enable scheduled sync |
- Click Connect
- Click Sync Now to start the initial sync
Your Nextcloud connector is now configured. Initial indexing may take a while depending on the size of the directory tree.
Managing the Integration
Viewing Sync Status
Navigate to Settings → Integrations to view last sync time, the number of indexed items, and any errors for each Nextcloud source. Click Configure for details.Sync Modes
| Mode | Description |
|---|---|
| Full | Walks the entire configured directory tree (used for initial sync) |
| Incremental | Uses ETag change detection to fetch only modified files since last sync |
Removing the Integration
- Navigate to Settings → Integrations
- Click Configure against the Nextcloud source
- Click Delete Permanently
Troubleshooting
Authentication failed
Authentication failed
The username or app password is incorrect, or the user lacks access to
base_path.Solution: Verify the credentials in Nextcloud and confirm the user can browse base_path via the web UI. Regenerate the app password if needed.Files not appearing in search
Files not appearing in search
Common causes:
- Files outside
base_path - Extension filtered out by allowlist/denylist
- File larger than
max_file_size
Sync is slow on large trees
Sync is slow on large trees
Nextcloud servers sometimes refuse
Depth: infinity listings. The connector falls back to breadth-first Depth: 1 traversal, which makes one request per directory.Solution: Narrow base_path to a specific subdirectory, or restrict extensions with extension_allowlist.Security Considerations
- Read-only access: The connector only issues WebDAV
PROPFINDandGETrequests - App passwords: Use an app password, not the user’s main password — it can be revoked independently
- Encrypted storage: Credentials are encrypted at rest in Omni
What’s Next
Search Your Data
Learn how to search across your files
AI Assistant
Ask questions about your documents
Add More Connectors
Connect additional data sources