> 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/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-batch-interface.md).

# Publish a Batch Interface

A batch interface runs a workflow for multiple rows of input. Each row has its own inputs, status, and output. Use it to process a collection without submitting each item through a separate form.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2F9B2kdRqUjyMIBtSa8O1Q%2FG058.mp4?alt=media&token=37b420d8-65c0-46c8-be6b-4c271af9b8e0>" %}

## Before you start

Configure the workflow inputs and output before selecting the Batch interface.

## Configure the batch columns

Choose the Batch interface and map its input and output columns.

![Batch input and output columns](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/t7mIQitJ9o4and6uH0Uv/assets/g058-g058-01-interface.png)

Set readable column aliases, then save the interface before entering rows. Before sharing it, configure [Security](/guides-and-quickstarts/interfaces-and-end-user-experiences/interface-authentication-and-access.md) and complete the required [publication process](/guides-and-quickstarts/releases-and-environments/publish-and-unpublish-a-project.md).

## Add or import rows

Use Add Run to enter the items you want to process.

![Batch input row controls](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/feiXFHT4pkFOKc26W0EX/assets/g058-g058-02-rows.png)

Each row supplies a separate set of workflow inputs.

Open the table menu to find import and export controls.

![Batch input row controls](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/PbhK9KN6cOQVZSHSOH1A/assets/g058-g058-03-menu.png)

Match the import columns to the input columns you configured. Start with one representative row and inspect its mapped values before importing the rest. Keep your source table so you can correct and retry failed rows without losing the original inputs.

## Run individual rows

Use a row’s run control to process that item.

![Individual batch row execution](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/Inb4E4a6TTneTVX49UXd/assets/g058-g058-04-first.png)

Its status and output show the result for that row.

Use the same run control on another row when you want to process it separately.

![Individual batch row execution](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/EvJflW1o62gcmnB4Oycy/assets/g058-g058-05-second.png)

Rows can complete with different results or errors.

## Review row results

Review the status and output columns before exporting results.

![Batch row status and output](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/AwNeInleH3HfZR6Oh1aJ/assets/g058-g058-06-third.png)

Investigate missing outputs or failed rows before using the exported data.

## Run the batch

Select Run Batch to process the table.

![Batch execution status and output](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/EKkmmiMPFFgHyVYiXmVP/assets/g058-g058-07-batch.png)

Review each row’s status and output after execution.

## Distinguish table imports from file inputs

Importing a CSV into the batch table creates rows of workflow inputs. Uploading a CSV for an agent to analyze treats it as a file. Choose the approach that matches the task.

When a row needs a file input, check its mapped file value in a representative run. Do not assume a file attached elsewhere is available to every row. [Let an agent work with uploaded files](/guides-and-quickstarts/interfaces-and-end-user-experiences/let-an-agent-work-with-uploaded-files.md) explains the shared agent file setup and download checks.

## Important behavior

Each row supplies a separate set of workflow inputs. A failed row needs its own investigation even when other rows complete.

## Continue

* [Interface authentication and access](/guides-and-quickstarts/interfaces-and-end-user-experiences/interface-authentication-and-access.md)
* [Inspect project analytics](/guides-and-quickstarts/evaluations-and-observability/inspect-project-analytics.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-batch-interface.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.