> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/workflow/build-workflow-steps/use-step-outputs-and-return-results.md).

# Use step outputs and return results

A step output is the result of an action. Later steps can use it, and a component workflow can expose results back to the app.

## Inspect an output before binding it

1. Configure a step with a representative test input.
2. Test the step.
3. Inspect its result: is it a single record, a list, a scalar value, or an error?
4. Open the next action's value picker and select the field it needs.

For example, read a ticket, then pass its record ID into an update action. Do not bind an entire response object to a field expecting one ID.

## Configure the workflow result

The workflow output configuration can use the last step's output or selected outputs from specific steps.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FAZ2qMQLZBce2cvZF0MkT%2Fzdfcbfty.png?alt=media\&token=ae14351b-a081-4793-9a26-a484ec9d1e96)

1. Open the workflow's output configuration.
2. Use the last step's result when it is the value the caller needs.
3. Otherwise, choose the specific step output.
4. Bind the resulting value in the app where the workflow result is available.

Use the functions modal if the result needs to be combined or transformed.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2F5ZGnt2NeQ9KUVKwD6qzJ%2Fzdxbtdr.png?alt=media\&token=0de21291-cb79-4fc8-84c7-bbc5e5955831)

## Test every result shape

Check a normal record, an empty lookup, and a failed operation. Do not let a missing result become an unfiltered update. If a branch does not execute, do not assume its step produced an output.

If the result appears in the test panel but not in the app, check both the workflow output selection and the app binding. See [testing](/workflow/test-and-troubleshoot/test-steps-and-complete-workflows.md) and [conditions](/workflow/build-workflow-steps/add-conditions-and-branches.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.jetadmin.io/workflow/build-workflow-steps/use-step-outputs-and-return-results.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.