> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/workflow-builder/apps/reducto.md).

# Reducto

**Reducto** is an integration that provides advanced document and data processing capabilities. It is often used for parsing, extracting, editing, and splitting documents or data files, as well as managing asynchronous jobs related to these operations. Reducto is especially useful for workflows that require automated document understanding, transformation, or extraction.

***

### Available Actions

| Action Name            | Description (Summary)                                                            |
| ---------------------- | -------------------------------------------------------------------------------- |
| **Parse**              | Parses a document or file to extract structured data or text.                    |
| **Async Parse**        | Submits a document for parsing and returns a job ID for later retrieval.         |
| **Extract**            | Extracts specific information or sections from a document.                       |
| **Async Extract**      | Submits an extraction job and returns a job ID for asynchronous processing.      |
| **Edit**               | Applies edits or transformations to a document.                                  |
| **Async Edit**         | Submits an edit job for asynchronous processing.                                 |
| **Split**              | Splits a document into multiple parts based on rules or structure.               |
| **Retrieve Parse Job** | Retrieves the result of a previously submitted async parse job using its job ID. |
| **Cancel Job**         | Cancels an ongoing asynchronous job by job ID.                                   |
| **Configure Webhook**  | Sets up a webhook to receive notifications about job status or completion.       |

***

### How to Use the Reducto Node

1. **Choose the Action:**
   * Select the Reducto node in your workflow and pick the action that matches your use case (e.g., Parse, Extract, Edit, Split).
2. **Provide Inputs:**
   * For most actions, you will need to provide a file, document, or text input. Some actions may require additional parameters (such as extraction rules, edit instructions, or split criteria).
3. **Asynchronous Jobs:**
   * For async actions, you will receive a job ID. Use the "Retrieve Parse Job" or similar action to check the status or get the result when processing is complete.
4. **Webhooks (Optional):**
   * If you want to be notified when a job is done, use the "Configure Webhook" action to set up a callback URL.
5. **Connect to Output or Downstream Nodes:**
   * The results from Reducto actions can be sent to Output nodes, LLM nodes, or further processing nodes in your workflow.

***

### Example Use Cases

* **Document Parsing:** Automatically extract tables, text, or metadata from uploaded PDFs or Word documents.
* **Data Extraction:** Pull out specific fields (like names, dates, or totals) from invoices or forms.
* **Document Splitting:** Break up large documents into smaller, manageable sections for further analysis.
* **Automated Editing:** Redact sensitive information or reformat documents before sharing.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stackai.com/workflow-builder/apps/reducto.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.