---
title: "DocuPipe integration for LuumenAI"
url: "https://www.luumen.ai/integrations/docupipe/"
entity: SoftwareIntegration
category: "AI & automation"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# DocuPipe integration for LuumenAI

Parse documents, pull structured data, and check extraction results from the terminal

## What LuumenAI can do with DocuPipe

LuumenAI connects to DocuPipe with an API token and exposes 13 tools (8 read-only · 3 write · 2 destructive). Reads answer immediately; writes are shown as a plan and require approval by default, configurable per tool by an administrator.

## Key facts

- Authentication: API token
- Tools available: 13 tools (8 read-only · 3 write · 2 destructive)
- Plan: available on all plans
- Category: AI & automation

## About DocuPipe with LuumenAI

Connect DocuPipe and your agent can see what has been parsed, which extraction schemas exist, and what each standardization returned. Ask for the structured fields from last night's invoice batch, or check why a job is still running. When something needs to change — a new document uploaded, an extraction started, a schema created — the agent shows the plan first and waits for your approval.

## Example tools

Read-only (8 in total):

- `DOCUPIPE_FIND_DOCUMENTS` — Browse documents by dataset and creation time, or search filenames and document IDs when query is provided.
- `DOCUPIPE_FIND_JOBS` — Retrieve one asynchronous job by ID, or list and filter jobs when job_id is omitted.
- `DOCUPIPE_GET_ACCOUNT_USAGE` — Return current plan and credit state together with job counts and credits consumed by job type, optionally including daily usage.
- `DOCUPIPE_GET_DOCUMENT` — Retrieve a processed document, including processing state, parsed content, page count, metadata, and file details.
- `DOCUPIPE_GET_SCHEMA` — Retrieve one extraction schema and its full JSON Schema definition by ID.
- `DOCUPIPE_GET_STANDARDIZATION` — Retrieve one completed standardization as structured JSON, including extraction data and field metadata.
- `DOCUPIPE_LIST_SCHEMAS` — List extraction schemas available to the connected workspace, optionally including each full JSON Schema payload.
- `DOCUPIPE_LIST_STANDARDIZATIONS` — List structured extraction results, filtered by schema, document, or up to 1000 known standardization IDs.

Write and destructive (5 in total, approval required by default):

- `DOCUPIPE_CREATE_SCHEMA` — Create a reusable extraction schema from a valid JSON Schema and optional extraction guidelines.
- `DOCUPIPE_DELETE_DOCUMENT` — Permanently delete one previously submitted DocuPipe document by ID.
- `DOCUPIPE_DELETE_DOCUMENTS` — Permanently delete multiple previously submitted DocuPipe documents by ID in one batch.
- `DOCUPIPE_STANDARDIZE_DOCUMENT` — Start V3 agentic structured extraction for one processed document and return the job and standardization IDs.
- `DOCUPIPE_UPLOAD_DOCUMENT` — Submit one local file or remote file URL for asynchronous parsing.

## Frequently asked questions

### How does LuumenAI connect to DocuPipe?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in DocuPipe on its own?

Read actions answer immediately. Anything that writes is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool.

### Is there an audit trail?

Every call to DocuPipe — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/docupipe/