Overview
What Gets Indexed
| Source | Content |
|---|---|
| Documents | Full OCR text extracted by Paperless-ngx |
| Classification | Correspondent, document type, tags, storage path, archive serial number |
| Custom fields | Resolved to human-readable field names |
| Notes | User annotations with author and timestamp |
| Dates | Created, added, and modified timestamps |
How It Works
- You provide a Paperless-ngx base URL and API token
- The connector fetches documents via the Paperless-ngx REST API
- Full syncs retrieve all documents; incremental syncs fetch only documents modified since the last run
- Incremental state is checkpointed periodically so large syncs can resume
The connector is strictly read-only — it never modifies documents, tags, or metadata in your Paperless-ngx instance.
Prerequisites
Before setting up the Paperless-ngx connector, ensure you have:- Paperless-ngx instance reachable from the Omni network
- An API token with read access to documents, tags, correspondents, document types, storage paths, and custom fields
- Omni deployment with the Paperless connector service running (profile:
paperless)
Setup
Step 1: Create an API Token
- Sign in to Paperless-ngx as the user Omni will connect as
- Go to Settings → API → API Tokens
- Create a new token and copy it — it will only be shown once
Step 2: Connect in Omni
- Navigate to Settings → Integrations in Omni
- Find Paperless-ngx and click Connect
- Enter the connection details:
- Base URL: Your Paperless-ngx instance (e.g.
https://paperless.example.com) - API Key: The token from Step 1
- Base URL: Your Paperless-ngx instance (e.g.
- Click Connect
- Click Sync Now to start the initial sync
Your Paperless-ngx connector is now configured. Initial indexing time depends on the number of documents in your instance.
Managing the Integration
Viewing Sync Status
Navigate to Settings → Integrations to view last sync time, number of indexed documents, and any errors. Click Configure for details.Sync Modes
| Mode | Description |
|---|---|
| Full | Fetches all documents from the instance (used for initial sync) |
| Incremental | Fetches only documents modified since the last sync (tracked via last_sync_at) |
Removing the Integration
- Navigate to Settings → Integrations
- Click Configure against the Paperless-ngx source
- Click Delete Permanently
Troubleshooting
Authentication failed
Authentication failed
The API token is incorrect, expired, or lacks the required permissions.Solution: Verify the token in Paperless-ngx at Settings → API → API Tokens and regenerate if needed. Ensure the token’s user has read access to documents and their related resources.
Documents not appearing in search
Documents not appearing in search
Common causes:
- Sync has not yet completed
- The API token’s user doesn’t have permission to view the documents
Custom fields missing
Custom fields missing
Custom fields are resolved through a separate API call. If the token lacks access to the custom fields endpoint, they will not appear.Solution: Grant the token’s user read access to custom fields in Paperless-ngx.
Security Considerations
- Read-only access: The connector only issues
GETrequests to the Paperless-ngx API - API tokens: Use a dedicated service user and token so access 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 documents
AI Assistant
Ask questions about your scanned documents
Add More Connectors
Connect additional data sources