# File Processor

A file upload and processing block that lives in the Order Form header. Handles file upload + custom processing logic tied to the transaction payload — distinct from the simpler **Attachments** block which just attaches files without processing.

The exact processing behaviour depends on how your implementation team has configured it for your workflow.

## Available in

* Order Form modules **only**

## When to use

* Workflows where uploaded files need processing before becoming attachments — for example, parsing a CSV of items, validating a vendor invoice, or transforming a document.
* Custom upload flows specific to your business that go beyond simple file attachment.

For straightforward "attach this file to the order" use cases, use **Attachments** instead.

## Settings

Configuration depends on your implementation. Common options include:

| Setting              | Description                                                                    |
| -------------------- | ------------------------------------------------------------------------------ |
| **File types**       | Accepted file formats.                                                         |
| **Processing rules** | What the block does with uploaded files (parsing, validation, transformation). |
| **On complete**      | What happens after processing finishes.                                        |

## How it works

The block is a wrapper around custom processing logic. At a high level:

1. The user uploads a file.
2. The block runs the configured processing logic against it.
3. The result is written to the order's payload (e.g. parsed line items, validated metadata, attached document IDs).
4. Downstream blocks read the processed result.

Because the processing rules are implementation-specific, ask your implementation team how File Processor is configured for your workflow.

{% hint style="info" %}
File Processor and **CSV Import** overlap in some scenarios — both can ingest a file. Use CSV Import for the standard "import line items from CSV" path; use File Processor for custom processing that doesn't fit that shape.
{% endhint %}

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Attachments</strong></td><td>For simple file attachment without custom processing.</td><td><a href="/pages/cmDBwRLTAhy4sPsvNMwU">/pages/cmDBwRLTAhy4sPsvNMwU</a></td></tr><tr><td><strong>CSV Import</strong></td><td>For importing line items from a CSV file.</td><td><a href="/pages/3J3BhOMsnonrsRzcbDVt">/pages/3J3BhOMsnonrsRzcbDVt</a></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.in8sync.com/client-admin-guide/active-workflows/getting-started/transaction-components/file-processor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.