Skip to main content
The Nextcloud connector enables Omni to index and search files stored in a Nextcloud instance via WebDAV. It’s designed for self-hosted and managed Nextcloud deployments alike.

Overview

What Gets Indexed

How It Works

  1. You provide a Nextcloud server URL, username, and app password
  2. The connector walks the configured directory tree via WebDAV PROPFIND
  3. Full and incremental syncs use ETag-based change detection
  4. Removed files are detected automatically on each sync
  5. 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

  1. Sign in to Nextcloud as the user Omni will connect as
  2. Go to SettingsSecurityDevices & sessions
  3. Enter a name (e.g. omni) and click Create new app password
  4. Copy the generated password — it will not be shown again
Create a dedicated service user with read-only access to the directories you want indexed. This keeps Omni’s access scoped and easy to revoke.

Step 2: Connect in Omni

  1. Navigate to SettingsIntegrations in Omni
  2. Find Nextcloud and click Connect
  3. 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
  4. Optionally configure advanced settings:
  1. Click Connect
  2. Click Sync 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 SettingsIntegrations to view last sync time, the number of indexed items, and any errors for each Nextcloud source. Click Settings for details and sync history.

Sync Modes

Removing the Integration

  1. Navigate to SettingsIntegrations
  2. Click Settings against the Nextcloud source
  3. Click Delete Permanently

Troubleshooting

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.
Common causes:
  • Files outside base_path
  • Extension filtered out by allowlist/denylist
  • File larger than max_file_size
Solution: Check the source configuration in SettingsIntegrationsNextcloud and trigger a manual sync.
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 PROPFIND and GET requests
  • 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