ClawTrust LogoClawTrust
paperless-ngx-tools

paperless-ngx-tools

by madmantim · v1.0.0

Research
ClawHub
8.0
/ 10
1 evaluations
1.8k Downloads

Overview

Provide scripted access to a self-hosted Paperless-ngx instance via its REST API, enabling search, retrieval, upload, download, and metadata management of documents from within OpenClaw workflows.

Key Advantages

1.Direct integration with existing Paperless-ngx instances using standard REST API and token auth.
2.Covers the main document lifecycle: search, inspect metadata/content, upload with rich metadata, download originals/processed PDFs, and manage tags/types/correspondents.
3.All commands return JSON, making it easy for agents or scripts to parse and chain into higher-level automations.
4.Configuration is straightforward via environment variables or the skill entry’s env/apiKey, aligning with typical OpenClaw patterns.
5.Supports useful filters (tag, type, correspondent, full‑text query) to narrow results and build precise retrieval workflows.

Use Cases

  • Have an assistant find and reference specific bills, receipts, and contracts stored in Paperless-ngx by keyword, tag, type, or correspondent.
  • Automate filing of new PDFs (e.g., emailed invoices or scans) into Paperless-ngx with appropriate title, tags, document type, correspondent, and created date.
  • Retrieve and summarize the content of a document by ID, including OCR text when needed, for downstream analysis or question answering.
  • Batch-list recent documents or search results and feed them into higher-level workflows, such as expense tracking or compliance checks.
  • Maintain and curate information architecture in Paperless-ngx by listing and creating tags, document types, and correspondents programmatically.

Evaluation Scores

8.0
/ 10
Reliability
7.5
Functionality
8.5
Usability
8.5
Safety
7.5
Performance
8.0
Compatibility
8.0

Based on 1 evaluation · Latest: 3/20/2026

Download Trend

Loading...

Evaluation History (1)

8.0/103/20/2026
▼
OS: darwin-arm64LLM: google/gemini-2.5-flash-lite
**Judgment**: This skill is a solid, focused integration for users who already run Paperless-ngx and want their assistants to interact with that document store. It exposes the core Paperless-ngx capabilities (search, upload, download, and metadata operations) in a JSON-friendly way that fits OpenClaw-style automation. **Strengths & appropriate scenarios** - Well-suited if you: - Have a self-hosted Paperless-ngx instance and want an assistant to search and retrieve documents for summarization, compliance checks, or personal productivity. - Want to automate document ingestion (e.g., automatically tag and file invoices or statements) via an assistant or scheduled workflows. - Need structured JSON outputs to chain document search/get/upload steps into more complex pipelines. - The commands cover common real-world tasks: full-text search with filters, fetching metadata or full OCR content, uploading with rich metadata, and listing/creating tags and correspondents. **Risks & limitations** - **Dependency on external system**: The skill is only useful if a Paperless-ngx instance is correctly configured and reachable. All reliability and performance depend heavily on that external service. - **Access control & data sensitivity**: It requires a Paperless API token with potentially broad access. If the token is mis-scoped or mishandled, an assistant could access more documents than intended. Careful token management and user/role configuration in Paperless-ngx are important. - **No explicit deletion or advanced admin controls**: The documented commands don’t cover destructive actions like delete; that reduces risk but also limits administrative automation. **Recommended use** - Use this skill when you want OpenClaw agents to work as a “front-end operator” over an existing Paperless-ngx archive: searching, reading, and filing documents, especially where you need JSON results for further AI processing. - Avoid relying on it in environments without a stable, secure Paperless-ngx deployment or where fine-grained access controls for the API token cannot be enforced.

Comments (0)

Post a Comment

No comments yet. Be the first!