> 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/technical-reference/interfaces-and-conversations/interface-inputs-and-output-mapping.md).

# Interface Inputs and Output Mapping

Interface fields collect user input and display selected workflow outputs. Map them explicitly so the interface shows the result you intend to deliver.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2F4y3Cpz8SQRNpFfFItnFu%2FG055.mp4?alt=media&token=e0aef030-2c30-435f-83d4-af30b65155bc>" %}

## Before you begin

An editable interface and a workflow with defined inputs and outputs.

## Key concepts

| Term        | Definition                                                                                                                                                        |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Interface   | The user-facing form, chat, batch view, or other supported access surface for a project. Its fields and security settings are distinct from editing the workflow. |
| Input field | A value collected from a user or client for execution. Map its displayed label to the correct workflow input key.                                                 |
| Schema      | A definition of fields, types, required values, and supported constraints. Use it to validate the shape of data; it does not establish factual correctness.       |
| Node        | A configured processing, input, output, or control step in a workflow. Inspect its inputs and result independently when tracing a problem.                        |

## Configuration options

| Option         | Purpose                                                                       | Behavior                                                                       |
| -------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| Output mapping | Selection of a node’s returned field for another step or the final interface. | A successful intermediate result is not automatically visible to the end user. |

## Map interface inputs and outputs

1. Choose the interface type and configure its visible input fields.
2. Map each field to the corresponding workflow input. Select the outputs to display.

![Use Fields to map the workflow input and output to the chat interface.](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/CAbhn63sC5UD7eFJbqDv/assets/g055-g055-02-fields.png)

Use Fields to map the workflow input and output to the chat interface.

3. Run the interface and inspect both submitted values and the displayed result.

The user can supply the required information and receive the intended output.

## Map file uploads

Select the intended **Files** input as well as the text input and final output. In Chat Assistant, **Show attachment icon** controls the visible paperclip; it does not select the Files input in **Fields**. **Required** controls whether users must supply a file.

Mapping the upload is one step. The agent also needs a file reference in its Prompt and the appropriate file-processing configuration. See [Let an agent work with uploaded files](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/let-an-agent-work-with-uploaded-files.md) for a complete example. Test the actual interface upload, rather than relying only on builder Test Files.

## Behavior and limitations

A node result is not automatically a visible interface output. Labels shown to users can differ from workflow field keys. Check required fields and file types before publishing. Show only the output fields that the audience needs.

## Related resources

[Publish a Chat Assistant](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-chat-assistant.md)

[Chat Messages, Conversations, and Session Identity](https://docs.stackai.com/technical-reference/interfaces-and-conversations/chat-messages-conversations-and-session-identity.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/technical-reference/interfaces-and-conversations/interface-inputs-and-output-mapping.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.
